Methods and systems for provisioning settings of a media playback device

ABSTRACT

A system is provided for streaming media content in a vehicle. The system includes a personal media streaming appliance system configured to connect to a media delivery system and receive media content from the media delivery system at least via a cellular network. The media delivery system is configured to link a user media streaming account with a particular personal media streaming appliance to provide personalized media content to the appliance. Media contexts are assigned to multiple preset settings automatically so that the personal media streaming appliance system is configured to output personalized media content upon first use.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation application of U.S. application Ser.No. 15/968,154, filed Apr. 20, 2018, now U.S. Pat. No. 10,367,687,issued Jul. 30, 2019, which is incorporated by reference herein in itsentirety.

BACKGROUND

Many people enjoy consuming media content while travelling or duringother activities. When driving, for example, drivers and passengerslisten to audio content, such as songs, albums, podcasts, audiobooks,and other types of audible content from devices that are built into thevehicle such as terrestrial and satellite radios and fixed media playersthat can playback media content stored on CDs, USB drives, or SD cards.Some vehicles have internet access and can stream or download mediacontent.

Alternatively, a mobile device, such as a smartphone or a tablet runningmusic streaming applications can be used. However, mobile devices arenot well suited for a vehicle environment for various reasons, such aslegal restrictions and sophisticated user interfaces that are notconvenient for use in a vehicle.

Typical media content services, devices, and applications for providingmedia content require multiple steps to prepare an account associatedwith the media content service, the device, and application in order toprovide personalized media content to a user. For example, it is commonfor users to be required to log into their device, establish wirelessconnections, and/or log into their account. Preferences have to be setby the user to provide a personalized media content experience. Evenonce a device is logged into a music streaming service, at least theinitial use of the service is not completely personalized for the user.

Many users desire a personalized media consuming experience. Forexample, a user can access almost limitless catalogs of media contentthrough various free or fee-based media delivery services, such as mediastreaming services. Users can use mobile devices or other media playbackdevices to access large catalogs of media content. Due to such largecollections of media content, it is desired to make it possible tocustomize a selection of media content to match users' individual tastesand preferences so that users can consume their favorite media contentwhile traveling in a vehicle.

Many vehicles include a built-in media playback device, such as a radioor a fixed media player, such as a player that can play media contentfrom a CD, USB drives, or SD cards. However, the media content that isdelivered using these built in vehicle media playback devices is greatlylimited and is not flexible or customizable to the user.

Alternatively, a mobile device, such as a smartphone or a tablet, can beused by a user to enjoy a personalized and flexible music consumingexperience in a vehicle by running music streaming applications thereon.However, the music streaming application is not automatically ready torun and play media content, and the user needs to pick up the mobiledevice and open the music streaming application and control asophisticated user interface to play media content.

One technical challenge associated with providing personalized mediacontent to a device in a vehicle is provisioning the device. Userstypically need to provide one or more inputs to a new media streamingdevice or application in order for personalized content to be played bythe device or application.

US 2002/0046084 describes an internet radio device for portableapplications and uses such as in an automobile. The internet radiodevice is configured by a user after purchase using a remote computerwith an internet connection. The device accesses the internet to receiveupdates to configurations.

US 2010/0077094 describes a system and method for updating media contentin a vehicle. Media content is received through a home network and isstored on a device in the vehicle. The media content can be updatedusing an application operated by a user.

No technical solution has been found to the problem of provisioning amedia playback device while it is within the supply chain channel priorto delivery.

There exists a need for a media playback system that is provisioned atthe early stages of the supply chain so that upon arrival it isprovisioned for use and control of personalized media content playback.

SUMMARY

In general terms, the present disclosure relates to provisioning of apersonal media streaming appliance. In one possible configuration and bynon-limiting example, the personal media streaming appliance is set upto play personalized media content upon first use of the appliancewithout additional input from a user. Various aspects are described inthis disclosure, which include, but are not limited to, the followingaspects.

One aspect is a method for customizing a personal media streamingappliance (PMSA). A media delivery system receives a user accountidentifier associated with a user media streaming account. The mediadelivery system also receives an appliance identifier associated withthe PMSA. The user account identifier and appliance identifier arelinked together. One or more media contexts are assigned to settings ofthe PMSA. At least one of the settings is associated with a presetbutton the PMSA. A preset signal is received at the media deliverysystem from the PMSA. The preset signal includes at least a presetbutton identifier and a user account identifier. The media deliverysystem retrieves media content matching a media context assigned to thesetting associated with the preset button corresponding to the presetbutton identifier. The media content is communicated to the PMSA forplayback.

Another aspect is a system for providing personalized media content to aPMSA. The system includes a media delivery system. The media deliverysystem includes a media content server having a processing device, amemory device, and a media server application. The media serverapplication is configured to provide a media streaming service. Themedia delivery system further includes a personal media streamingappliance server having a processing device, a memory device, and apersonal media streaming appliance configuration engine. The personalmedia streaming appliance configuration engine is configured to link auser media streaming account to a PMSA and determine personalizedcontent to provide to the PMSA upon first use.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example system for provisioning settings of apersonal media streaming appliance (PMSA) system.

FIG. 2 is a block diagram of an example embodiment of the personal mediastreaming appliance (PMSA) system of FIG. 1.

FIG. 3 is a block diagram of an example embodiment of the media deliverysystem of FIG. 1.

FIG. 4 is a block diagram of an example embodiment of the user computingdevice of FIG. 1.

FIG. 5 is a block diagram of an example embodiment of the vendorcomputing device of FIG. 1.

FIG. 6 schematically illustrates an example embodiment of the PMSAsystem of FIG. 1.

FIG. 7A illustrates an example embodiment of the PMSA system includingan appliance identification marker.

FIG. 7B illustrates a further example embodiment of the PMSA systemincluding an appliance identification marker

FIG. 8 is a flow diagram illustrating an example method of provisioninga PMSA system ordered in association with a user media streamingaccount.

FIG. 9 is a flow diagram illustrating an example method of provisioninga PMSA system at the time of first use.

FIG. 10 is a flow diagram illustrating an example method of assigningmedia contexts to preset settings of a PMSA system.

FIG. 11 illustrates an example data structure of a database of the mediadelivery system of FIG. 1.

FIG. 12 illustrates an example system for streaming media content forplayback in a vehicle.

FIG. 13 is a block diagram of an example embodiment of the vehicle mediaplayback system of FIG. 12.

FIG. 14 illustrates an example ecosystem for the PMSA system of FIG. 1.

FIG. 15 is a block diagram of the preset signal of FIG. 14.

FIG. 16 is a block diagram of the PMSA preset data of FIG. 14.

DETAILED DESCRIPTION

Various embodiments will be described in detail with reference to thedrawings, wherein like reference numerals represent like parts andassemblies throughout the several views.

As used herein, the term “media content” refers to audio content, videocontent, and combinations thereof. Examples of audio content includesongs, albums, playlists, radio stations, podcasts, audiobooks, andother audible media content items. Examples of video content includemovies, music videos, television programs, and other visible mediacontent items. In many cases, video content also includes audio content.

As used herein, the term “vehicle” can be any machine that is operableto transport people or cargo. Vehicles can be motorized ornon-motorized. Vehicles can be for public or private transport. Examplesof vehicles include motor vehicles (e.g., cars, trucks, buses,motorcycles), rail vehicles (e.g., trains, trams), tracked vehicles,watercraft (e.g., ships, boats), aircraft, human-powered vehicles (e.g.,bicycles), wagons, and other transportation means.

A user can drive a vehicle or ride as a passenger for travelling. Asused herein, the term “travel” and variants thereof refers to anyactivity in which a user is in transit between two locations.

As used herein, the term “provisioning” refers to a process in which adevice is prepared for operation by a user. Provisioning can includesteps such as building the device, installing software on the device,establishing connections with networks, and setting up user access. Insome instances, provisioning can include setting up user preferences andsettings for the device.

The present disclosure generally relates to providing a personal mediastreaming appliance (PMSA) system 110 that is personalized to aparticular user at the time the user first uses the PMSA. A mediastreaming account of the user is associated with the PMSA 110 before thefirst operation of the PMSA 110 to play media content. The user account240 provides information about the user's preferences for consumingmedia content. The user account 240 stores assignments of particularcontexts of media content with controls on the PMSA 110. This setupprovides the PMSA 110 with media content to play that the user is likelyto enjoy.

A media delivery system 112 associates the user's media streamingaccount 240 with the PMSA 110. This occurs before the PMSA 110 receivesany inputs to play media content. In some embodiments, the PMSA 110 isprovisioned with a particular user's media streaming account before thePMSA 110 is first operated to play media content.

Preset settings are automatically generated for each PMSA 110 based onthe associated user account 240. For example, preset buttons 412 on thePMSA 110 can be assigned media contexts that are selected based on ataste profile 242 associated with a user's media streaming account. Oneexample of a taste profile 242 provides a history of the user's mediaconsumption. Media content is selected that is similar to media contentthat is in the history of the user's media streaming account.

In one embodiment, a user computing device 102 receives an input to loginto the media streaming account. The media streaming account isassociated with a user operating the user computing device 102. The usercomputing device 102 then receives input to place an order for a PMSA110 to be delivered to an address of the user. The user computing device102 communicates the order to the media delivery system 112. The mediadelivery system 112 records this order. The order is recorded by linkingan order identifier (typically a number or other series of characters)with an account identifier associated with the user's account 240 (e.g.a unique account ID number or username).

The media delivery system 112 can then submit a request to a vendor tofulfill the order. In some instances, the media delivery system 112collects multiple orders for PMSA's and submits one request for multipleappliances to the vendor manufacturer. The request includes at least anorder number for each PMSA.

The manufacturer vendor records a unique appliance identifier 128 afterthe PMSA 110 is ready to ship. A vendor computing device 108 submitsthat appliance identifier 128 to the media delivery system 112. Theappliance identifier 128 can be a number or other series of characters.The appliance identifier 128 can be recorded by scanning a barcode or QRcode. The appliance identifier 128 is submitted along with itscorresponding order number to the media delivery system 112.

Upon receiving the appliance identifier 128, the media delivery system112 matches the order identifier with the account identifier. Theappliance identifier 128 corresponding to the order identifier is thenlinked to the account identifier in the user's account 240. The deviceidentifier is stored in a table along with the account identifier.

In another embodiment, a user can purchase a PMSA 110 from a retailer.In this example, the user account is associated with the PMSA 110 at thetime of purchase. The PMSA 110 still receives personalized settings bylinking to a user's media streaming account and will providepersonalized media content upon first use.

In either embodiment, the media delivery system 112 utilizes a usertaste profile 242 from the user account to assign contexts to each of aplurality of settings on the PMSA 110. The user's taste profile 242could change between the time that the PMSA 110 is ordered and when thePMSA 110 is delivered. As a result, the assigned contexts will beupdated so that the PMSA 110 will have the most up to datepersonalization settings upon first use.

In some embodiments, the appliance provides a simplified user interfaceso that a user can easily control playback of media content in a vehiclewhile maintaining his or her focus on other tasks such as driving ornavigating. For example, the appliance has a limited set of physicalcontrol elements that are intuitively controllable for playback of mediacontent with little (often only one) input. Examples of such physicalcontrol elements include a rotatable knob and one or morephysically-depressible buttons.

In some embodiments, the appliance also provides an output interfacethat can be easily connected to a vehicle audio system. Such outputinterfaces can include an auxiliary input port or Bluetooth. Outputinterfaces transmit media content from the appliance to the vehicleaudio system for playback in the vehicle.

FIG. 1 illustrates an example system 100 for provisioning a personalmedia streaming appliance (PMSA). The system 100 includes at least amedia delivery system 112, a network 116, an appliance identifyingcomputing device 102, 108A, 108B and a personal media streamingappliance (PMSA) 110. The media delivery system 112 operates to providemedia content through one or more media playback devices. Media playbackdevices are configured to play media content and can include thepersonal media streaming appliance (PMSA) system 110, a vehicle mediaplayback system 114, and the user computing device 102.

The media delivery system 112 includes at least an applianceprovisioning engine 126. The appliance provisioning engine 126 isfurther described in FIG. 3. In some embodiments, the applianceprovisioning engine 126 is part of a system independent of the mediadelivery system 112. The media delivery system 112 communicates withmultiple servers, computing devices, and other network enabled devices.

The appliance distributor server 106 receives communications from themedia delivery system 112 through the network 116. The appliancedistributor server 106 also communicates with a vendor computing device108. In some embodiments, the appliance distributor server 106 operateswithin a warehouse W.

In some embodiments, the vendor computing device 108A, 108B operates asan appliance identification device by using an appliance input device122. The appliance input device 122 can be, for example, a barcodescanner. The appliance input device 122 is used to input an applianceidentifier 128. An example of an appliance identifier 128 is a barcode,which is, for example, placed either directly on a PMSA 110 or itspackaging P.

In some embodiments, an order is received by a user computing device 102such as a laptop computer or a mobile device. The order data isassociated with a user account for playing media content. In an exampleembodiment, input is provided to the user computing device 102 to ordera PMSA 110, for example through a user interface of the user computingdevice 102. The order is, in turn, communicated to a media deliverysystem 112 via the network 116.

This order is received through the network 116 by the media deliverysystem 112. The media delivery system 112 then forwards the order to theappliance distributor server 106 for fulfillment at the warehouse W.

After the order is fulfilled in the warehouse, a confirmation message isreceived at the media delivery system 112. The confirmation message canbe received from the appliance distributor server 106, the vendorcomputing device 108A, or any source having information regarding thestatus of the appliance order.

The packaged PMSA 110 is transported via a carrier directly to theuser's address. For example, the PMSA 110 is transported on a truck T toan address specified in the order. In the example of FIG. 1, the addressmay be for the user U's home. It should be understood that othertransportation vehicles may be used in connection with the logistics ofdelivering the PMSA 110. For example, a plane, train, or otherautomobile, can be used instead of truck T and still be within the scopeof the invention.

In some embodiments, a confirmation message is received at the mediadelivery system 112 indicating that the PMSA 110 has been delivered atthe address specified in the order. The confirmation message can bereceived from a user computing device 102, the appliance distributorserver 106, a carrier computing device, or any other source havinginformation regarding the status of the appliance delivery.

In other examples, one or more units of PMSA 110 may be transported to aretailer R for distribution to customers. In such examples, the PMSA 110may be identified using an appliance ID input device 122 associated witha vendor computing device 108B at the retailer R. The vendor computingdevice 108B operates as an appliance identification device andcommunicates through the network 116 with the media delivery system 112to identify a PMSA 110 via an appliance identifier 128. As will bedescribed below, in some embodiments, this identification process can beused to link the PMSA 110 with a user account.

Once the PMSA 110 arrives at its destination address, it is ready to beinstalled in a vehicle V. At this stage, the PMSA 110 is powered on.Media content 124 associated with the user account is communicated tothe PMSA 110 and can be played over a vehicle media playback system 114.In some embodiments, the media content 124 is presented in the form of aplaylist that includes information sufficient to cause a media deliverysystem 112 to deliver media content 124 (e.g., by downloading it orstreaming).

The system 100 detects that a PMSA 110 has been purchased and associatesthe PMSA 110 with a media playback account that is associated with thepurchase. In turn, the system 100 links the media playback account tothe PMSA 110 so that upon the first use of the PMSA 110, personalizedmedia content is available for playback. In some embodiments, thepersonalized media content is available for playback in a vehicle Vwithout any additional set-up steps.

The PMSA system 110 operates to receive media content that is provided(e.g., streamed, transmitted, etc.) by a system external to the PMSAsystem 110, such as the media delivery system 112. The PMSA 110 can thentransmit the media content to the vehicle media playback system 114 forplayback. In some embodiments, the PMSA system 110 is a portable devicewhich can be carried into and used in the vehicle V. The PMSA system 110can be mounted to a structure of the vehicle V, such as the dashboard.In other embodiments, the PMSA system 110 can be configured to be builtin a structure of the vehicle V. An example of the PMSA system 110 isillustrated and described in more detail with reference to FIGS. 2 and6.

The vehicle media playback system 114 operates to receive media contentfrom the PMSA system 110. The vehicle media playback system 114generates a media output 124 to play the media content in the vehicle V.An example of the vehicle media playback system 114 is illustrated anddescribed in further detail herein, such as with reference to FIG. 13.

The network 116 is a data communication network through which the PMSAsystem 110 and the media delivery system 112 can communicate. In someembodiments, the user computing device 102 can also communicate with themedia delivery system 112 across the network 116. The network 116typically includes a set of computing devices and communication linksbetween the computing devices. The computing devices in the network 116use the links to enable communication among the computing devices in thenetwork. The network 116 can include one or more routers, switches,mobile access points, bridges, hubs, intrusion detection devices,storage devices, standalone server devices, blade server devices,sensors, desktop computers, firewall devices, laptop computers, handheldcomputers, mobile telephones, vehicular computing devices, and othertypes of computing devices.

In various embodiments, the network 116 includes various types ofcommunication links. For example, the network 116 can include wiredand/or wireless links, including cellular, Bluetooth, ultra-wideband(UWB), 802.11, ZigBee, and other types of wireless links. Furthermore,in various embodiments, the network is implemented at various scales.For example, the network 116 can be implemented as one or more vehiclearea networks, local area networks (LANs), metropolitan area networks,subnets, wide area networks (WAN) (such as the Internet), or can beimplemented at another scale. Further, in some embodiments, the network116 includes multiple networks, which may be of the same type or ofmultiple different types.

In some embodiments, the network 116 can also be used for datacommunication between other media playback devices and the mediadelivery system 112. Because the network 116 is configured primarily fordata communication between computing devices in the vehicle V andcomputing devices outside the vehicle V, the network 116 is alsoreferred to herein as an out-of-vehicle network for out-of-vehicle datacommunication.

FIG. 2 is a block diagram of an example embodiment of the PMSA system110 of the media streaming system 100 shown in FIG. 1. In this example,the PMSA system 110 includes a user input device 130, a display device132, a wireless data communication device 134, a movement detectiondevice 136, a location determining device 138, a media content outputdevice 140, an in-vehicle wireless communication device 142, a powersupply 144, a power input device 146, a processing device 148, and amemory device 150.

In some embodiments, the PMSA system 110 is a system dedicated forstreaming personalized media content in a vehicle environment. At leastsome embodiments of the PMSA system 110 have limited functionalitiesspecifically selected for streaming media content from the mediadelivery system 112 at least via the network 116 and/or for providingother services associated with the media content streaming service. ThePMSA system 110 may have no other general use such as found in othercomputing devices, such as smartphones, tablets, and other smartdevices.

For example, in some embodiments, when the PMSA system 110 is poweredup, the PMSA system 110 is configured to automatically activate asoftware application. The software application is configured to performthe media content streaming and media playback operations of the PMSAsystem 110 using at least one of the components, devices, and elementsof the PMSA system 110. In some embodiments, the software application ofthe PMSA system 110 is configured to continue running until the PMSAsystem 110 is powered off or powered down to a predetermined level.

The user input device 130 operates to receive a user input 152 forcontrolling the PMSA system 110. As illustrated, the user input 152 caninclude a manual input 154 and a voice input 156. In some embodiments,the user input device 130 includes a manual input device 160 and a sounddetection device 162.

The manual input device 160 operates to receive the manual input 154 forcontrolling playback of media content via the PMSA system 110. Inaddition, in some embodiments, the manual input 154 is received formanaging various pieces of information transmitted via the PMSA system110 and/or controlling other functions or aspects associated with thePMSA system 110.

In some embodiments, the manual input device 160 includes one or moremanual control elements configured to receive various manual controlactions, such as pressing actions and rotational actions. As describedherein, the physical input device 160 includes a manual control knob 410and one or more physical buttons 412, which is further illustrated anddescribed with reference to FIG. 6.

The sound detection device 162 operates to detect and record sounds fromproximate to the PMSA system 110. For example, the sound detectiondevice 162 can detect sounds including the voice input 156. In someembodiments, the sound detection device 162 includes one or moreacoustic sensors configured to detect sounds proximate to the PMSAsystem 110. For example, acoustic sensors of the sound detection device162 includes one or more microphones. Various types of microphones canbe used for the sound detection device 162 of the PMSA system 110.

In some embodiments, the voice input 156 is a user's voice forcontrolling playback of media content via the PMSA system 110. Inaddition, the voice input 156 manages various data transmitted via thePMSA system 110 and/or controlling other functions or aspects associatedwith the PMSA system 110.

In some embodiments, the sound detection device 162 is configured tocancel noises from the received sounds so that a desired sound (e.g.,the voice input 156) is clearly identified. For example, the sounddetection device 162 can include one or more noise-canceling microphoneswhich are configured to filter ambient noise from the voice input 156.In addition or alternatively, a plurality of microphones of the sounddetection device 162 are arranged at different locations in a body ofthe PMSA system 110 and/or oriented in different directions with respectto the body of the PMSA system 110, so that ambient noise is effectivelycanceled from the voice input 156 or other desired sounds beingidentified.

In some embodiments, the sounds detected by the sound detection device162 can be processed by the sound processing engine 180 of the PMSAsystem 110 as described below.

Referring still to FIG. 2, the display device 132 operates to displayinformation to the user U. Examples of such information include mediacontent playback information, notifications, and other information.

In some embodiments, the display device 132 operates as a display screenonly and is not capable of receiving a user input. By receiving themanual input 154 only via the manual input device 160 and disablingreceipt of manual input via the display device 132, the user interfaceof the PMSA system 110 is simplified so that the user U can control thePMSA system 110 while maintaining focus on other activities in thevehicle V. It is understood however that, in other embodiments, thedisplay device 132 is configured as a touch-sensitive display screenthat operates as both a display screen and a user input device. In yetother embodiments, the PMSA system 110 does not include a displaydevice.

As described herein, in some embodiments, the display device 132 isarranged at the manual input device 160. In other embodiments, thedisplay device 132 is arranged separate from the manual input device160.

The wireless data communication device 134 operates to enable the PMSAsystem 110 to communicate with one or more computing devices at a remotelocation that is outside the vehicle V. In the illustrated example, thewireless data communication device 134 operates to connect the PMSAsystem 110 to one or more networks outside the vehicle V, such as thenetwork 116. For example, the wireless data communication device 134 isconfigured to communicate with the media delivery system 112 and receivemedia content from the media delivery system 112 at least partially viathe network 116. The wireless data communication device 134 can be awireless network interface of various types which connects the PMSAsystem 110 to the network 116. Examples of the wireless datacommunication device 134 include wireless wide area network (WWAN)interfaces, which use mobile telecommunication cellular networktechnologies. Examples of cellular network technologies include LTE,WiMAX, UMTS, CDMA2000, GSM, cellular digital packet data (CDPD), andMobitex. In some embodiments, the wireless data communication device 134is configured as a cellular network interface to facilitate datacommunication between the PMSA system 110 and the media delivery system112 over cellular network.

The movement detection device 136 can be used to detect movement of thePMSA system 110 and the vehicle V. In some embodiments, the movementdetection device 136 is configured to monitor one or more factors thatare used to determine movement of the vehicle V. The movement detectiondevice 136 can include one or more sensors that are configured to detectmovement, position, and/or orientation of the PMSA system 110. As anexample, the movement detection device 136 is operable to determine anorientation of the PMSA system 110. The movement detection device 136can detect changes in the determined orientation and interpret thosechanges as indicating movement of the PMSA system 110.

In some embodiments, the movement detection device 136 includes anaccelerometer. In other embodiments, the movement detection device 136includes a gyroscope. Other sensors can also be used for the movementdetection device 136, such as a magnetometer, a GPS receiver, analtimeter, an odometer, a speedometer, a shock detector, a vibrationsensor, a proximity sensor, and an optical sensor (e.g., a light sensor,a camera, and an infrared sensor).

The location determining device 138 is a device that determines thelocation of the PMSA system 110. In some embodiments, the locationdetermining device 138 uses one or more of Global Positioning System(GPS) technology (which may receive GPS signals), Global NavigationSatellite System (GLONASS) technology, cellular triangulationtechnology, network-based location identification technology, Wi-Fipositioning systems technology, and combinations thereof.

The media content output device 140 is an interface that enables thePMSA system 110 to transmit media content to the vehicle media playbacksystem 114. Some embodiments of the PMSA system 110 do not have aspeaker and thus cannot play media content independently. In theseembodiments, the PMSA system 110 is not regarded as a standalone devicefor playing media content. Instead, the PMSA system 110 transmits mediacontent to another media playback device, such as the vehicle mediaplayback system 114 to enable the other media playback device to playthe media content, such as through the vehicle stereo system.

As illustrated, the PMSA system 110 (e.g., a media content processingengine 176 thereof in FIG. 2) can convert media content to a mediacontent signal 164, the media content output device 140 transmits themedia content signal 164 to the vehicle media playback system 114. Thevehicle media playback system 114 can play the media content based onthe media content signal 164. For example, the vehicle media playbacksystem 114 operates to convert the media content signal 164 into aformat that is readable by the vehicle media playback system 114 forplayback.

In some embodiments, the media content output device 140 includes anauxiliary (AUX) output interface 166 and a wireless output interface168.

The AUX output interface 166 is configured to connect the PMSA system110 to the vehicle media playback system 114 via a cable (e.g., a mediacontent output line 450 in FIG. 6) of the PMSA system 110. In someembodiments, as illustrated in FIG. 6, the media content output line 450extending from the PMSA system 110 is connected to an input connector456 (e.g., an auxiliary input jack or port) of the vehicle mediaplayback system 114. As illustrated herein, the media content outputline 450 can be of various types, such as an analog audio cable or a USBcable.

The wireless output interface 168 is configured to connect the PMSAsystem 110 to the vehicle media playback system 114 via a wirelesscommunication protocol. In some embodiments, the wireless outputinterface 168 is configured for Bluetooth connection. In otherembodiments, the wireless output interface 168 is configured for othertypes of wireless connection. In some embodiments, the wireless outputinterface 168 is incorporated into, or implemented with, the in-vehiclewireless communication device 142. For example, when the media contentoutput device 140 wirelessly transmits media content to the vehiclemedia playback system 114, the in-vehicle wireless communication device142 can be used to implement the wireless output interface 168 of themedia content output device 140.

Referring still to FIG. 2, the in-vehicle wireless communication device142 operates to establish a wireless data communication betweencomputing devices in a vehicle V.

The power supply 144 is included in the example PMSA system 110 and isconfigured to supply electric power to the PMSA system 110. In someembodiments, the power supply 144 includes at least one battery. Thepower supply 144 can be rechargeable. For example, the power supply 144can be recharged using the power input device 146 that is connected toan external power supply. In some embodiments, the power supply 144 isincluded inside the PMSA system 110 and is not removable from the PMSAsystem 110. In other embodiments, the power supply 144 is removable fromthe PMSA system 110.

The power input device 146 is configured to receive electric power tomaintain activation of components of the PMSA system 110. As describedherein, the power input device 146 is connected to a power source of thevehicle V (e.g., a vehicle power supply 440 in FIG. 6) and use theelectric power from the vehicle V as a primary power source to maintainactivation of the PMSA system 110 over an extended period of time, suchas longer than several minutes.

The processing device 148, in some embodiments, comprises one or morecentral processing units (CPU). In other embodiments, the processingdevice 148 additionally or alternatively includes one or more digitalsignal processors, field-programmable gate arrays, or other electroniccircuits.

The memory device 150 typically includes at least some form ofcomputer-readable media. Computer readable media includes any availablemedia that can be accessed by the PMSA system 110. By way of example,computer-readable media include computer readable storage media andcomputer readable communication media.

Computer readable storage media includes volatile and nonvolatile,removable and non-removable media implemented in any device configuredto store information such as computer readable instructions, datastructures, program modules, or other data. Computer readable storagemedia includes, but is not limited to, random access memory, read onlymemory, electrically erasable programmable read only memory, flashmemory and other memory technology, compact disc read only memory, blueray discs, digital versatile discs or other optical storage, magneticstorage devices, or any other medium that can be used to store thedesired information and that can be accessed by the PMSA system 110. Insome embodiments, computer readable storage media is non-transitorycomputer readable storage media.

Computer readable communication media typically embodies computerreadable instructions, data structures, program modules or other data ina modulated data signal such as a carrier wave or other transportmechanism and includes any information delivery media. The term“modulated data signal” refers to a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, computer readable communication mediaincludes wired media such as a wired network or direct-wired connection,and wireless media such as acoustic, radio frequency, infrared, andother wireless media. Combinations of any of the above are also includedwithin the scope of computer readable media.

The memory device 150 operates to store data and instructions. In someembodiments, the memory device 150 stores instructions for a mediacontent cache 172, a caching management engine 174, a media contentprocessing engine 176, a manual input processing engine 178, a soundprocessing engine 180, a voice interaction engine 182, and an appliancesetting configuration engine 184.

Some embodiments of the memory device 150 include the media contentcache 172. The media content cache 172 stores media content items, suchas media content items that have been received from the media deliverysystem 112. The media content items stored in the media content cache172 may be stored in an encrypted or unencrypted format. In someembodiments, the media content cache 172 also stores metadata aboutmedia content items such as title, artist name, album name, length,genre, mood, era, etc. The media content cache 172 can further storeplayback information about the media content items and/or otherinformation associated with the media content items.

The caching management engine 174 is configured to receive and cachemedia content in the media content cache 172 and manage the mediacontent stored in the media content cache 172. In some embodiments, whenmedia content is streamed from the media delivery system 112, thecaching management engine 174 operates to cache at least a portion ofthe media content into the media content cache 172 so that at least aportion of the cached media content can be transmitted to the vehiclemedia playback system 114 for playback. In other embodiments, thecaching management engine 174 operates to cache at least a portion ofmedia content into the media content cache 172 while online so that thecached media content is retrieved for playback while the PMSA system 110is offline.

The media content processing engine 176 is configured to process themedia content that is received from the media delivery system 112, andgenerate the media content signal 164 usable for the vehicle mediaplayback system 114 to play the media content. The media content signal164 is transmitted to the vehicle media playback system 114 using themedia content output device 140, and then decoded so that the vehiclemedia playback system 114 plays the media content in the vehicle V.

The manual input processing engine 178 operates to receive the manualinput 154 via the manual input device 160. In some embodiments, when themanual input device 160 is actuated (e.g., pressed or rotated) uponreceiving the manual input 154, the manual input device 160 generates anelectric signal representative of the manual input 154. The manual inputprocessing engine 178 can process the electric signal and determine theinput (e.g., command or instruction) corresponding to the manual input154 to the PMSA system 110. In some embodiments, the manual inputprocessing engine 178 can perform a function requested by the manualinput 154, such as controlling playback of media content. The manualinput processing engine 178 can cause one or more other engines toperform the function associated with the manual input 154.

The sound processing engine 180 is configured to receive sound signalsobtained from the sound detection device 162 and process the soundsignals to identify different sources of the sounds received via thesound detection device 162. In some embodiments, the sound processingengine 180 operates to filter voice input 156 from noises included inthe detected sounds. Various noise cancellation technologies, such asactive noise control or cancelling technologies or passive noise controlor cancelling technologies, can be used for filter the voice input fromambient noise. By using one or more of these techniques, the soundprocessing engine 180 provides sound processing customized for use in avehicle environment.

In some embodiments, a recording of sounds captured using the sounddetection device 162 can be analyzed using speech recognition technologyto identify words spoken. The words may be recognized as commands thatalter the playback of media content and/or other functions or aspect ofthe PMSA system 110. In some embodiments, the words and/or therecordings may also be analyzed using natural language processing and/orintent recognition technology to determine appropriate actions to takebased on the spoken words. Additionally or alternatively, the soundprocessing engine 180 may determine various sound properties about thesounds proximate to the PMSA system 110 such as volume, dominantfrequency or frequencies, etc. These sound properties may be used tomake inferences about the environment proximate to the PMSA system 110.

The voice interaction engine 182 operates to cooperate with the mediadelivery system 112 (e.g., a voice interaction server 204 thereof asillustrated in FIG. 3) to identify a command (e.g., a user intent) thatis conveyed by the voice input 156. In some embodiments, the voiceinteraction engine 182 transmits the voice input 156 that is detected bythe sound processing engine 180 to the media delivery system 112. Themedia delivery system 112 operates to determine a command intended bythe voice input 156. In other embodiments, at least some of thedetermination process of the command can be performed locally by thevoice interaction engine 182.

In addition, some embodiments of the voice interaction engine 182 canoperate to cooperate with the media delivery system 112 (e.g., the voiceinteraction server 204 thereof) to provide a voice assistant thatperforms various voice-based interactions with the user. Voice-basedinteractions include voice feedbacks, voice notifications, voicerecommendations, and other voice-related interactions and services.

The appliance setting configuration engine 184 operates to send andreceive signals from the media delivery system 112 to modify presetsettings at the PMSA system 110. Customized settings for controls of thePMSA 110 such as preset buttons 412 can be personalized by inputsreceived at the PMSA 110 or by modifying personalization settingsthrough the media delivery system 112.

FIG. 3 is a block diagram of an example embodiment of the media deliverysystem 112 of FIG. 1. The media delivery system 112 includes a mediacontent server 200, a personal media streaming appliance (PMSA) server202, and a voice interaction server 204.

The media delivery system 112 comprises one or more computing devicesand provides media content to the PMSA system 110 and, in someembodiments, other media playback devices, as well. In addition, themedia delivery system 112 interacts with the PMSA system 110 to providethe PMSA system 110 with various functionalities.

In at least some embodiments, the media content server 200, the PMSAserver 202, and the voice interaction server 204 are provided byseparate computing devices. In other embodiments, the media contentserver 200, the PMSA server 202, and the voice interaction server 204are provided by the same computing device(s). Further, in someembodiments, at least one of the media content server 200, the PMSAserver 202, and the voice interaction server 204 is provided by multiplecomputing devices. For example, the media content server 200, the PMSAserver 202, and the voice interaction server 204 may be provided bymultiple redundant servers located in multiple geographic locations.

Although FIG. 3 shows a single media content server 200, a single PMSAserver 202, and a single voice interaction server 204, some embodimentsinclude multiple media servers, multiple PMSA servers, and/or multiplevoice interaction servers. In these embodiments, each of the multiplemedia servers, multiple PMSA servers, and multiple voice interactionservers may be identical or similar to the media content server 200, thePMSA server 202, and the voice interaction server, respectively, asdescribed herein, and may provide similar functionality with, forexample, greater capacity and redundancy and/or services from multiplegeographic locations. Alternatively, in these embodiments, some of themultiple media servers, the multiple PMSA servers, and/or the multiplevoice interaction servers may perform specialized functions to providespecialized services. Various combinations thereof are possible as well.

The media content server 200 transmits stream media 210 (FIG. 2) tomedia playback devices such as the PMSA system 110. In some embodiments,the media content server 200 includes a media server application 212, aprocessing device 214, a memory device 216, and a network access device218. The processing device 214 and the memory device 216 may be similarto the processing device 148 and the memory device 150, respectively,which have each been previously described. Therefore, the description ofthe processing device 214 and the memory device 216 are omitted forbrevity purposes.

The network access device 218 operates to communicate with othercomputing devices over one or more networks, such as the network 116.Examples of the network access device include one or more wired networkinterfaces and wireless network interfaces. Examples of such wirelessnetwork interfaces of the network access device 218 include wirelesswide area network (WWAN) interfaces (including cellular networks) andwireless local area network (WLANs) interfaces. In other examples, othertypes of wireless interfaces can be used for the network access device218.

In some embodiments, the media server application 212 is configured tostream media content, such as music or other audio, video, or othersuitable forms of media content. The media server application 212includes a media stream service 222, a media application interface 224,and a media data store 226. The media stream service 222 operates tobuffer media content, such as media content items 230A, 230B, and 230N(collectively 230), for streaming to one or more streams 232A, 232B, and232N (collectively 232).

The media application interface 224 can receive requests or othercommunication from media playback devices or other systems, such as thePMSA system 110, to retrieve media content items from the media contentserver 200. For example, in FIG. 2, the media application interface 224receives communication from the PMSA system 110, such as the cachingmanagement engine 174 thereof, to receive media content from the mediacontent server 200.

In some embodiments, the media data store 226 stores media content items234, media content metadata 236, media contexts 238, user accounts 240,and taste profiles 242. The media data store 226 may comprise one ormore databases and file systems. Other embodiments are possible as well.

As discussed herein, the media content items 234 (including the mediacontent items 230) may be audio, video, or any other type of mediacontent, which may be stored in any format for storing media content.

The media content metadata 236 provides various information associatedwith the media content items 234. In some embodiments, the media contentmetadata 236 includes one or more of title, artist name, album name,length, genre, mood, era, etc.

The media content metadata 236 operates to provide various pieces ofinformation associated with the media content items 234. In someembodiments, the media content metadata 236 includes one or more oftitle, artist name, album name, length, genre, mood, era, etc.

Explicit metadata refers to factual or explicit information relating tomusic. Explicit metadata may include album and song titles, artist andcomposer names, other credits, album cover art, publisher name andproduct number, and other information. Explicit metadata is generallynot derived from the music itself or from the reactions or opinions oflisteners.

At least some of the metadata 236, such as explicit metadata (names,credits, product numbers, etc.), for a large library of songs or trackscan be evaluated and provided by one or more third party serviceproviders. Explicit metadata may include numerical, text, pictorial, andother information. Explicit metadata may also be stored in an XML orother file. All or portions of the metadata may be stored in separatefiles associated with specific tracks. All or portions of the metadata,such as acoustic fingerprints and/or description vectors, may be storedin a searchable data structure, such as a k-D tree or other databaseformat.

Referring still to FIG. 3, each of the media contexts 238 is used toidentify one or more media content items 234. In some embodiments, themedia contexts 238 are configured to group one or more media contentitems 234 and provide a particular context to the group of media contentitems 234. Some examples of the media contexts 238 include albums,artists, playlists, and individual media content items. By way ofexample, where a media context 238 is an album, the media context 238can represent that the media content items 234 identified by the mediacontext 238 are associated with that album.

As described above, the media contexts 238 can include playlists 239.The playlists 238 are used to identify one or more of the media contentitems 234. In some embodiments, the playlists 238 identify a group ofthe media content items 234 in a particular order. In other embodiments,the playlists 238 merely identify a group of the media content items 234without specifying a particular order. Some, but not necessarily all, ofthe media content items 234 included in a particular one of theplaylists 238 are associated with a common characteristic such as acommon genre, mood, or era.

In some embodiments, media content items in a playlist 238 can be playedby selecting the playlist 238 via a media playback device, such as thePMSA system 110. The media playback device then operates to communicatewith the media delivery system 112 so that the media delivery system 112retrieves the media content items identified by the playlist 238 andtransmits data for the media content items to the media playback devicefor playback.

In some embodiments, the playlist 238 includes a playlist title and alist of content media item identifications. The playlist title is atitle of the playlist, which can be received through inputs on a usercomputing device 102. The list of content media item identificationsincludes one or more media content item identifications (IDs) that referto respective media content items 234.

The user accounts 240 are used to identify users of a media streamingservice provided by the media delivery system 112. In some embodiments,a user account 240 allows for authentication before providing access tothe media delivery system 112. In some embodiments, input for login canbe received at different devices (e.g., the PMSA system 110 and the usercomputing device 102) to access data associated with the user account inthe media delivery system 112. User authentication information, such asa username, an email account information, a password, and othercredentials, can be used to access a user media streaming account 240.

The user accounts 240 include data for devices associated with each useraccount. The user accounts 240 data store keeps track of the devicesthat can access the media content server 200 using a particular useraccount. In some embodiments, the user accounts 240 data store recordsorder numbers for new devices that are ordered in order to associate thenew devices with particular user accounts. Data stored in the useraccounts 240 data store is further described with respect to FIG. 11.

The taste profiles 242 contain records indicating media content tastesof users. A taste profile 242 can be associated with a user account andused to maintain an in-depth understanding of the music activity andpreferences associated with a user account. Libraries and wrappers canbe accessed to create taste profiles from a media library of the useraccount, social website activity and other specialized databases to minemusic preferences.

In some embodiments, each taste profile 242 is a representation of mediaconsumption activities. The media consumption activities can include awide range of information such as artist plays, song plays, skips, datesof listen, songs per day, playlists, play counts, start/stop/skip datafor portions of a song or album, contents of collections, rankings,preferences, or other mentions received via a client device, or othermedia plays, such as websites visited, book titles, movies watched,playing activity during a movie or other presentations, ratings, orterms corresponding to the media, such as “comedy”, “sexy”, etc. Inaddition, the taste profiles 242 can include other information. Forexample, the taste profiles 242 can include libraries and/or playlistsof media content items associated with the user account.

The taste profiles 242 can be used for a number of purposes. One use oftaste profiles is for creating personalized playlists (e.g., personalplaylisting). An API call associated with personal playlisting can beused to return a playlist customized to a particular user account. Forexample, the media content items listed in the created playlist areconstrained to the media content items in a taste profile associatedwith the particular user account.

Yet another use case is for personalized recommendation, where thecontents of a taste profile are used to represent an individual's taste.This API call uses a taste profile as a seed for obtainingrecommendations or playlists of similar artists.

Yet another example use case for taste profiles is referred to asuser-to-user recommendation. This API call is used to discover userswith similar tastes by comparing the similarity of taste profile item(s)associated with users.

A taste profile 242 can represent a single user account or multipleusers' accounts. Conversely, a single user account can have multipletaste profiles 242. For example, one taste profile can be generated inconnection with media content play activity of a user account, whereasanother separate taste profile can be generated for the same useraccount based on the selection of media content items and/or artists fora playlist.

Referring still to FIG. 3, the PMSA server 202 operates to providevarious functionalities to the PMSA system 110. In some embodiments, thePMSA server 202 includes a personal media streaming appliance (PMSA)server application 250, a processing device 252, a memory device 254,and a network access device 256. The processing device 252, the memorydevice 254, and the network access device 256 may be similar to theprocessing device 214, the memory device 216, and the network accessdevice 218, respectively, which have each been previously described. Insome embodiments, the PMSA server 202 is independent of the mediadelivery system 112.

In some embodiments, the PMSA server application 250 operates tointeract with the PMSA system 110 and enable the PMSA system 110 toperform various functions. Such functions can include receiving a manualinput, displaying information, providing notifications, performing powermanagement, providing location-based services, and authenticating loginsfor the PMSA system 110. The PMSA server application 250 can interactwith other servers, such as the media content server 200 and the voiceinteraction server 204, to execute such functions.

The PMSA server application 250 includes a personal media streamingappliance configuration engine 258. The PMSA configuration engine 258operates to configure settings for a PMSA that are personalized to auser's account. For example, the PMSA configuration engine 258 assignsmedia contexts to preset settings of the PMSA. Functionality of the PMSAconfiguration engine 258 is further described with respect to FIGS. 10and 14.

The PMSA configuration engine 258 includes an appliance provisioningengine 126. The appliance provisioning engine 126 operates to set up thepreset settings of a PMSA before its first operation. The applianceprovisioning engine 126 links a PMSA with a particular user account sothat preset settings are customized to an account of that user. Theappliance provisioning engine 126 is further described with respect toFIG. 14. In some embodiments, the appliance provisioning engine 126 isindependent of the PMSA server application 250.

Referring still to FIG. 3, the voice interaction server 204 operates toprovide various voice-related functionalities to the PMSA system 110. Insome embodiments, the voice interaction server 204 includes a voiceinteraction server application 270, a processing device 272, a memorydevice 274, and a network access device 276. The processing device 272,the memory device 274, and the network access device 276 may be similarto the processing device 214, the memory device 216, and the networkaccess device 218, respectively, which have each been previouslydescribed.

In some embodiments, the voice interaction server application 270operates to interact with the PMSA system 110 and enable the PMSA system110 to perform various voice-related functions, such as voice feedbackand voice notifications. In some embodiments, the voice interactionserver application 270 is configured to receive data (e.g.,speech-to-text (STT) data) representative of a voice input received viathe PMSA system 110. The voice interaction server application 270 canprocess the data to interpret a command (e.g., a request orinstruction). In some embodiments, at least one of the media contentserver 200, the PMSA server 202, and the voice interaction server 204may be used to perform one or more functions corresponding to thecommand.

FIG. 4 is a block diagram of an example embodiment of the user computingdevice 102. The user computing device 102 includes a system memory 280,a network access device 282, a processing device 284, a mass storagedevice 286, and an input/output device 288.

The network access device 282 operates to communicate with othercomputing devices over one or more networks, such as the network 116.Examples of the network access device 282 include wired networkinterfaces and wireless network interfaces. Wireless network interfacesinclude infrared, BLUETOOTH® wireless technology, 802.11a/b/g/n/ac,cellular or other radio frequency interfaces wireless wide area network(WWAN) interfaces (including cellular networks), and wireless local areanetwork (WLANs) interfaces.

The processing device 284 in some embodiments comprises one or morecentral processing units (CPU). In other embodiments, the processingdevice 284 additionally or alternatively includes one or more digitalsignal processors, field-programmable gate arrays, or other electroniccircuits.

The mass storage device 286 includes at least an operating system 290, aweb browser application 292, and a music playback application 294.

The operating system 290 provides general functionality to the usercomputing device 102. This is software that allows for basic tasks forbe performed such as scheduling tasks, executing applications, andcontrolling peripherals.

The web browser application 292 operates to present a user interface onthe user computing device 102 for interacting with the internet. The webbrowser application 292 may be employed to order a PMSA 110.

The media playback application 294 receives inputs for commands tolisten to media content, adjust settings for media content playback, andprovide profile information for a user account. The media playbackapplication 294 receives inputs from an input/output device 288 toselect media content to play. The media playback application 294 canalso record the media content that is consumed to send to the mediadelivery system 112 to build a taste profile 242 for the user account.The media playback application 294 includes user settings 296, which canbe adjusted to reflect the preferences of a user associated with theuser account. Inputs are received at an input/out device 288 thatinstruct the media playback application 294 to modify settings for mediaplayback. Updated settings are stored in the user settings 296 database.

Examples of user settings 296 include assigning media contexts to eachof a plurality of presets associated with physical controls on a PMSA.In some examples, a playlist, artist, album, genre, or radio station canbe assigned to a particular preset button on the PMSA. Other settingscan include having a preference for shuffling music tracks as they areplayed in the context.

The input/output device 288 includes an appliance ID input device 122.The appliance ID input device 122 can include a keyboard, a touchscreen, a camera, a QR reader, or a barcode scanner. The appliance IDinput device 122 is used to identify a PMSA 110 appliance identifier128. In some embodiments, the user U sets up the PMSA 110 for use withhis or her media streaming account. Input is received at a usercomputing device 102 to log into a user account. The appliance ID inputdevice 122 allows for receipt of the appliance identifier 128 into theuser computing device 102. The music playback application 294 thencommunicates the user account information and the appliance identifier128 to the media delivery system 112.

FIG. 5 illustrates a schematic block diagram of a vendor computingdevice 108. The vendor computing device 108A of FIG. 1 was shown in awarehouse W while another vendor computing device 108B was shown in thecontext of a retailer R. The vendor computing device 108A in thewarehouse W communicates with a media delivery system 112 and anappliance distributor server 106 via network 116. The vendor computingdevice 108B at the retailer R communicates with the media deliverysystem 112. The vendor computing device 108 includes a system memory302, a network access device 304, a processing device 306, a massstorage device 308, and an input/out device 310.

The system memory 302, network access device 304, and processing device306 are similar to the system memory 280, network access device 282, andprocessing device 284 described above in FIG. 4.

The mass storage device 308 includes an operating system 314 and deviceidentification software application 316. The operating system 314 issimilar to the operating system 290 of FIG. 4. The device identificationsoftware application 316 receives identifying information for a deviceor appliance from the appliance ID input device 122. The deviceidentification software application operates to communicate theappliance ID along with an order identifier or account identifier to themedia delivery system 112. The media delivery system 112 then pairs eachappliance or device ID with a user's media streaming account.

The input/output device 310 includes an appliance ID input device 122.The appliance ID input device 122 is used to input an applianceidentifier 128 to the vendor computing device 108. Examples of applianceidentifiers 128 are shown in FIGS. 7A and 7B. Appliance identifiers 128can include barcodes, QR codes, serial numbers, bokodes, and RFID tags.The appliance ID input device 122 is configured to scan, read, orreceive other input of an appliance identifier 128. In some embodiments,the input/output device 310 includes more than one appliance ID inputdevice 122.

In the context of a warehouse W, the vendor computing device 108A isused to receive an appliance identifier 128 associated with a PMSA 110using the appliance ID input device 122. The appliance identifier 128identifies the PMSA 110 and that information is communicated to theappliance distributor server 106. The appliance distributor server 106then communicates that information to the media delivery system 112. Themedia delivery system 112 receives the appliance identifier 128 alongwith a confirmation that an order has been fulfilled. The applianceidentifier 128 can be associated with a user account by the mediadelivery system 112.

In the context of a retailer R, a vendor computing device 108B is usableto receive an appliance identifier 128 for a PMSA 110 that is being soldin a retail store. The vendor computing device 108B receives theappliance identifier 128 through the appliance ID input device 122. Anemployee of the retailer R communicates with the user U to obtain theiraccount information. Login information is received through inputs at thevendor computing device 108B such as a keyboard. The applianceidentifier 128 information and the user's account information are bothcommunicated through the network 116 to the media delivery system 112,where the device ID and user's account ID are associated and stored inthe media delivery system 112 as described in further detail withrespect to FIGS. 8 and 11.

FIG. 6 schematically illustrates an example embodiment of the PMSAsystem 110 of FIG. 1. In this example, the PMSA system 110 includes apersonal media streaming appliance (PMSA) 400 and a docking device 402.

As described herein, the PMSA system 110 is sized to be relatively smallso that the PMSA system 110 can be easily mounted to a structure (e.g.,a dashboard or head unit) of the vehicle V. By way of example, the PMSAsystem 110 is configured to be smaller than a typical mobile computingdevice, such as a smartphone. Further, the PMSA 400 provides asimplified user interface for controlling playback of media content. Forexample, the PMSA 400 has a limited set of physical control elements,such as a single rotary knob and one or more physical buttons.

The PMSA 400 is configured to include at least some of the devices ofthe PMSA system 110 as illustrated with reference to FIG. 2. In someembodiments, the PMSA 400 includes all of the devices of the PMSA system110 as illustrated in FIG. 2.

As illustrated also in FIG. 2, some embodiments of the PMSA 400 includethe user input device 130 that includes the manual input device 160 andthe sound detection device 162. Some embodiments of the manual inputdevice 160 include a control knob 410 and one or more physical buttons412.

In some embodiments, the control knob 410 is configured to bemaneuverable in multiple ways. For example, the control knob 410provides a plurality of regions on a knob face 414 that areindependently depressible upon receiving a pressing action against theknob face 414. In the illustrated example, the control knob 410 has fiveregions 416 (e.g., up, down, left, right, and middle) that areseparately depressible. At least some of the regions 416 are configuredto receive inputs of different commands (e.g., requests orinstructions).

In other embodiments, the control knob 410 is configured to bemanipulated in different ways, such as tilting in multiple directions orsliding in multiple directions.

In addition, the control knob 410 is configured to be rotatable. Forexample, the control knob 410 can be rotated with respect to a body 420of the PMSA 400. The control knob 410 can be rotatable in bothdirections 422 (e.g., clockwise and counterclockwise). In otherembodiments, the control knob 410 is configured to rotate in only onedirection.

The control knob 410 is used to receive inputs for controlling playbackof media content. In addition or alternatively, the control knob 410 canbe used to receive inputs for other purposes or functions.

The physical buttons 412 are configured to be depressed upon receiving apressing action against the physical buttons 412. In the illustratedexample, the PMSA 400 has four physical buttons 412A-412D. In someembodiments, each of the physical buttons 412 is configured to receive asingle command. In other embodiments, at least one of the physicalbuttons 412 is configured to receive multiple commands.

In some embodiments, the physical buttons 412 are used as buttons thatare preset to be associated with particular media content context,thereby facilitating playback of such media content. In theseembodiments, the physical buttons 412 are also referred to as presetbuttons 412.

In addition, the PMSA 400 also includes the display screen 132. In someembodiments, the display screen 132 is arranged at the knob face 414 ofthe control knob 410. As described herein, in some embodiments, thedisplay screen 132 does not include a touch sensitive display screen,and is configured as a display device only. In other embodiments,however, the display screen 132 can be configured to be touch sensitiveand receive an input through the display screen 132 as well.

Referring still to FIG. 6, the docking device 402 is configured to mountthe PMSA 400 to a structure of the vehicle V. The docking device 402 isconfigured to removably mount the PMSA 400 thereto. The docking device402 is further configured to attach to a structure of the vehicle V(FIG. 13) so that the PMSA 400 is positioned at the structure of thevehicle V.

In some embodiments, an interface between the PMSA 400 and the dockingdevice 402 is configured to prevent the PMSA 400 from rotating relativeto the docking device 402 when the control knob 410 is manipulated. Forexample, the docking device 402 has a portion (e.g., a front portion ofthe docking device 402) configured to interlock a corresponding portionof the PMSA 400 (e.g., a rear portion of the PMSA 400) when the PMSA 400is mounted to the docking device 402 such that the portion of thedocking device 402 and the corresponding portion of the PMSA 400 formthe interface therebetween.

In addition or alternatively, the PMSA 400 and the docking device 402include magnetic materials at the interface therebetween so that thePMSA 400 and the docking device 402 are magnetically coupled to eachother.

In some embodiments, the docking device 402 includes one or moreelectrical contacts 430 that are electrically connected to correspondingelectrical contacts (not shown in FIG. 6) of the PMSA 400 when the PMSA400 is mounted to the docking device 402. Such electrical connectionbetween the PMSA 400 and the docking device 402 is provided for variousfunctions.

First, as described herein, the PMSA 400 does not include a batterysufficient for a prolonged use without an external power supply. In someembodiments, the PMSA 400 is primarily powered by a vehicle power supply440. In some embodiments, the docking device 402 has a power receivingline 444 for connection to the vehicle power supply 440. For example,the power receiving line 444 extends from the docking device 402 and hasa power connector 446 at a free end that is configured to mate with avehicle power outlet 442 (e.g., a 12V auxiliary power outlet) of thevehicle power supply 440. As such, the docking device 402 receiveselectric power from the vehicle power supply 440 via the power receivingline 444, and the electrical connection between the PMSA 400 and thedocking device 402 is configured to deliver electric power from thedocking device 402 to the PMSA 400.

Second, as described herein, the PMSA 400 does not have a speaker and isdesigned to transmit media content signals to the vehicle media playbacksystem 114 so that the media content is played through the vehicle mediaplayback system 114. In some embodiments, the docking device 402includes a media content output line 450 (also referred to herein as amedia content output cable) (e.g., an auxiliary (AUX) output) configuredto connect with the vehicle media playback input connector 456 (e.g., anauxiliary (AUX) port) of the vehicle media playback system 114. Thedocking device 402 is configured to receive media content signals fromthe PMSA 400 via the electrical connection between the PMSA 400 and thedocking device 402, and transmit the signals to the vehicle mediaplayback system 114 via the media content output line 450. In theillustrated embodiment, the power receiving line 444 and the mediacontent output line 450 are combined to be a single line extending fromthe docking device 402 until the power connector 446, and the mediacontent output line 450 further extends (or branches out) from the powerconnector 446 and terminates at a media output connector 452. The mediaoutput connector 452 is configured to connect to the vehicle mediaplayback input connector 456 of the vehicle media playback system 114.In other embodiments, the media content output line 450 and the powerreceiving line 444 extend separately from the docking device 402.

In other embodiments, one or more of the power receiving line 444 andthe media content output line 450 are directly connected to, and extendfrom, the PMSA 400 so that electric power is directly supplied to thePMSA 400 without the docking device 402 involved, and that the mediacontent is directly transmitted to the vehicle media playback system 114without passing through the docking device 402.

Third, the electrical connection between the PMSA 400 and the dockingdevice 402 can be used to detect connection between the PMSA 400 and thedocking device 402.

The PMSA system 110 can be provided to a user U in at least threedifferent ways. In the first method, input is received at a usercomputing device 102 such as a laptop or a mobile device to log into auser media streaming account 240. Input is received at the usercomputing device 102 to place an order for a PMSA system 110 through themedia streaming account. The order is then linked to the user's accountat the time of ordering. The appliance 110 is shipped directly from themanufacturer or distributor to an address provided with the order.During the shipping process, the appliance is paired to the useraccount. The PMSA 110 is programmed to receive instructions from themedia delivery system 112 immediately upon powering on. The PMSA 110 canimmediately play personalized media content upon receiving input at aphysical control such as the physical buttons 412.

In another method, the PMSA system 110 is shipped to a retailer, such asthe retailer R of FIG. 1. The retailer R offers the PMSA system 110 forsale to customers that may or may not already have a media streamingaccount. At the retailer, an employee assists with setting up the PMSA110 for use with a media streaming account.

For new users, the employee assists by providing inputs to a vendorcomputing device 108B to set up a new account. Commands are received atthe vendor computing device 108B and communicated to the media deliverysystem 112 to link the account with the PMSA 110. In such instances, thePMSA will automatically update with settings that are configured to playpopular music or otherwise provide media content to be available forplayback upon first use of the PMSA 110.

For existing users of a media streaming account, the past mediaconsumption activity associated with the media streaming account isevaluated and used. Media contexts are selected at the media deliverysystem 112 that will be associated with the physical controls of thePMSA 110 so that upon first use of the device, the PMSA 110 will playmedia content selected specifically for the user account.

In yet another method, the PMSA system 110 is either shipped to the userU or the user U purchases the PMSA system 110 at a retailer. However,the user's media streaming account is not linked to the PMSA in advance.In such instances, input is received at a user computing device 102 tolog into the user's media streaming account. Input is received at theuser computing device 102 identifying the PMSA 110. For example, aninput of a QR code can be received. The media delivery system 112receives the appliance identifying information and associates the PMSA110 with the user account. Then, immediately after the PMSA 110 ispowered on, media content selected for the media streaming account isreceived from the media delivery system 112 and played on the PMSA 110.

Regardless of the method by which the user U receives the PMSA system110, the PMSA will be provided with an appliance identifier 128 of somesort. The appliance identifier 128 could be placed on packaging of thePMSA 110 or be directly placed on the appliance itself.

FIGS. 7A & FIG. 7B show two examples of placement of the applianceidentifier 128. In the example of FIG. 7A, the appliance identifier 128is a barcode placed on the outside of a packaging P which encloses thepersonal media streaming appliance PMSA 110. The appliance identifierbarcode 128 can be scanned by an employee of a warehouse. The warehousevendor computing device 108B submits an appliance ID to the mediadelivery system 112 where the device ID is paired with an account ID.This can be performed using a computing device such as the vendorcomputing device 108 of FIG. 1.

In other examples, a retailer R may scan the appliance identifier 128 atthe time of a purchase. The retailer R obtains user account information,scans the appliance identifier 128 with the appliance ID input device122 and submits both the user account number and appliance ID numberthrough the network 116 to the media delivery system 112 where it isrecorded. In yet another embodiment, a user may set-up the PMSA 110 foruse with their media streaming account themselves. The user computingdevice 102 receives the appliance identifier 128 through a camera orinput on a keyboard.

FIG. 7B shows an embodiment in which the appliance identifier 128 isplaced directly on the PMSA 110. In this example, the applianceidentifier 128 is a QR code affixed to a back surface of the PMSA 110.The appliance identifier 128 can be captured by a computing device in awarehouse, at a retailer, or with a user computing device 102 asdescribed above for FIG. 7A.

FIG. 8 illustrates a method flowchart for a method 500 of provisioning aPMSA for use with a user media streaming account. The method 500involves a user U placing an order for a PMSA 110 to be delivered to theuser for use in the user's vehicle V. The user has an existing mediastreaming account or signs up for a media streaming account at the timethat the user places the order for the PMSA 110. FIG. 8 shows the status502 of the ordering and shipping process. The system involved incompleting the steps of the method 500 include the user computing device102, the media delivery system 112, the appliance distributor server106, the vendor computing device 108, and the personal media streamingappliance 110. The status 502 indicates which steps of the method 500are performed during “placing order,” “preparing order,” “shippingorder,” and “order received.”

The method 700 begins when login information is received at the usercomputing device 102 at operation 504. The login information is receivedat the user computing device 102 through an input/output device 288.Examples of such input/output devices 288 include a keyboard, a mouse,and a touch screen. The login information includes at least a useraccount ID, such as the user account ID 930 described in FIG. 15.

At operation 506, input is received at the user computing device 102 foran appliance to be ordered. The input places an order for a PMSA 110that is associated with a user media streaming account.

At operation 508, the user computing device 102 submits an order for aPMSA. The media delivery system 112 receives the order at operation 509.The order is assigned an order ID at the time of submission. The orderID and user account ID are included in the order.

At operation 510, the order ID is linked to the user's account ID andrecorded at the media delivery system 112. In some embodiments, thelinked order ID and account ID are stored in a table such as one of thetables in the data structure 700 of FIG. 11. The order information isthen forwarded to the appliance distributor server 106.

At operation 512, the order is received at the appliance distributorserver 106. The order for the PMSA 110 is prepared at a manufacturer ordistributor warehouse. When a PMSA is ready to be shipped, a device IDfor the PMSA 110 is recorded using a vendor computing device 108 atoperation 514. The device ID is then communicated to the appliancedistributor server 106.

At operation 516, the device ID is forwarded from the appliancedistributor server 106 along with the order ID to the media deliverysystem 112.

At operation 517, the media delivery system 112 receives the device IDwith the order ID. The device ID and order ID can be included in aconfirmation message. In some embodiments, the confirmation message isreceived from the appliance distributor server 106. The device ID andorder ID can be received at the media delivery system 112 from othersources such a carrier computing device. The media delivery system 112links the device ID with the user account ID based on the common orderID at operation 518. The storage of the device ID is described furtherwith respect to FIG. 11.

While the order for the PMSA 110 is shipping, the media delivery system112 operates to set up the functionality of the PMSA 110 so that mediacontent played at the PMSA 110 will be personalized to the user accountwhen the PMSA 110 is first operated. At operation 520, the mediadelivery system 112 accesses the taste profile 242 of the user accountassociated with the user account ID. The taste profile 242 indicateswhich media contexts are most often utilized by the media streamingaccount. A media context can be one of an artist, an album, a playlist,and a radio station. The media delivery system 112 analyzes the tasteprofile 242 to identify media contexts.

At operation 522, the top contexts selected from the taste profile 242are assigned to preset settings of the PMSA. Each preset setting of thePMSA is associated with a particular input that can be received from thePMSA. For example, an input may be pressing a preset button or turningthe knob. A more detailed example of methods of assigning contexts topreset settings is described in FIG. 10.

In some embodiments, a confirmation message is received at the mediadelivery system 112 when the PMSA 110 is delivered at the addressspecified in the order. The confirmation message can be received fromany source having information regarding the delivery status of the PMSA110. For example, a carrier computing device or a user computing device102 could be the source of the confirmation message.

At operation 524, input is received at the personal media streamingappliance 110 from a physical control. The PMSA 110 may be installed ina vehicle V. The physical control can be, for example, a preset button412.

At operation 526, a preset signal 912 is submitted from the personalmedia streaming appliance 110 to the media delivery media system 112.The preset signal 912 is further described in FIG. 15.

At operation 528, the preset signal is received at the media deliverysystem 112. The media delivery system 112 processes the preset signal todetermine which media context is associated with the preset signal 912.

At operation 530, the context associated with the input is identified atthe media delivery system 112. In embodiments where the PMSA 110 isconfigured to play audio content, the context can be a music playlist, apodcast, an audiobook, an artist, an album, or a radio station.

At operation 532, the media delivery system 112 sends the media contentassociated with the selected context to the personal media streamingappliance 110.

At operation 534, the PMSA 110 receives the selected media content fromthe media delivery system 112.

At operation 536, the media delivery system 112 retrieves the mediacontent associated with the context of the selected preset.

At operation 536, the media content from the selected context is playedon the PMSA 110.

FIG. 9 illustrates a method flowchart for a method 540 of provisioning aPMSA for use with a user media streaming account. The method 540involves a user U purchasing a PMSA 110 from a retailer rather thanordering through the media delivery system 112. The user has an existingmedia streaming account or signs up for a media streaming account at thetime that the user purchases the PMSA 110. The system involved incompleting the steps of the method 540 include an applianceidentification device 102, 108, the media delivery system 112, and thepersonal media streaming appliance 110. The appliance identificationdevice can be a user computing device 102 or a vendor computing device108A, 108B, as shown in FIG. 1.

The method 540 begins when login information is received at theappliance identification device 102, 108 at operation 546. The user Umay input the login information into the appliance identification device102, 108 or an employee working for a retailer could input the logininformation for the user. Login information is received through aninput/output device 288. Examples of such devices include a keyboard, amouse, and a touch screen. The login information includes at least auser account ID, such as the user account ID 930 described in FIG. 15.In instances where the user does not already have a media streamingaccount, the user can set up a new account or an employee could assistthe user with setting up an account.

At operation 547, a user account ID is submitted to the media deliverysystem 112 through the network 116. The user account ID is associatedwith a user media streaming account.

At operation 548, the media delivery system 112 receives the useraccount ID and accesses the user account. In some instances, acommunication may be returned to the appliance identification device102, 108 to confirm successful login and provide a prompt to add a newdevice to the user account.

At operation 550, input of a device ID is received at the applianceidentification device 102, 108 and communicated to the media deliverysystem 112. The device ID is taken from a PMSA that is to be associatedwith a particular user's media streaming account. In some cases, theappliance identification device 102, 108 can include a bar code scannerto read a barcode with a unique identifier for the PMSA 110. In otherinstances, a camera could be used to capture a QR code or other uniqueidentifying symbol on the PMSA 110 or its packaging. Alternatively or inaddition to the scanning methods, the appliance identification device102, 108 could receive characters representing the device ID through akeyboard, touchscreen, or other input device.

At operation 552, the media delivery system 112 receives the device ID.In some embodiments, the device ID is received from the applianceidentification device 102, 108. The media delivery system 112 links thedevice ID with the user account ID. The storage of the device ID isdescribed further with respect to FIG. 11.

Similar to the method 500 of FIG. 8, the media delivery system 112operates to set up the functionality of the PMSA so that media contentplayed at the PMSA will be personalized to the user account upon firstoperation of the PMSA 110. However, the set up steps may occur during amuch shorter period of time because the PMSA 110 is not being shipped.

At operation 556, the media contexts are assigned to preset buttons 412of the PMSA. Each preset setting of the PMSA is associated with aparticular preset button. A more detailed example of methods ofassigning contexts to preset buttons is described in FIG. 10.

At operation 558 an input of a preset button is received at the PMSA110. A preset signal is submitted at operation 559. The preset signal isfurther described in FIG. 15.

At operation 562, the media delivery system 112 receives the presetsignal. The preset signal includes at least a device ID and presetbutton ID. At operation 560, the information from the preset signal isused to identify a media context assigned to the preset button.

At operation 561, the media content associated with the media context isretrieved by the media delivery system 112 and communicated to the PMSA110. The media content from the context assigned to the preset button isthen played on the PMSA 110 at operation 562.

FIG. 10 is a flow chart of an example method 600 of assigning mediacontexts to preset buttons on a PMSA associated with a user mediastreaming account.

At operation 602, the media delivery system 112 determines whether theuser account is new or existing. New accounts may be made just beforeoperating at PMSA 110, so there is no media playback history associatedwith the account. Existing user accounts typically have informationreflecting past media consumption activity.

For existing user accounts, the method proceeds to operation 606 where ataste profile 242 is accessed at the media delivery system 112. Thetaste profiles may be accessed from the taste profile 242 data storewithin the media data store 226 of the media server application 212 asshown in FIG. 3. A taste profile 242 reflects media consumptionpreferences based on the media consumption history of an account. Forexample, a history of listening to particular types of music couldindicate a preference for a particular musical genre or artist.

For new user accounts, the method proceeds to operation 610, where userprofile information is accessed. When setting up a new media streamingaccount, a prompt is presented to enter at least a minimal amount ofpersonal information for a user associated with the account. Forexample, such personal information could include one or more of a birthdate, a gender, and a location. In some embodiments, a prompt ispresented to provide information about media consumption preferencesthrough the use of a survey. For example, a prompt might requestselection of favorite music genres from a list. In another embodiment, aprompt is presented to log into a social media account to allow themedia streaming account to access information from the social mediaaccount. Information from the social media account could be used todetermine media consumption preferences.

At operation 612, the new profile information is compared to profileinformation from existing accounts of the media streaming service. Themedia consumption activity of user accounts having similar profileinformation is analyzed to determine which media contexts are preferred.

At operation 614, the media consumption activity of similar useraccounts is utilized to build a taste profile 242 for the new useraccount.

Regardless of whether the user account is new or existing, the methodthen proceeds to operation 618. The top “n” media contexts from thetaste profile are selected. “n” is a number that matches the number ofpreset buttons on a PMSA 110 that is associated with the user's mediastreaming account. For example, if the PMSA 110 has four preset buttons412 as shown in FIG. 6, four media contexts would be selected. The “top”media contexts can be selected based on media contexts that are used themost often by the user. Alternative methods of ranking are possible suchas the most recently played media contexts, or contexts that are mostfrequently saved to the user account.

At operation 620, the media contexts are assigned to the preset buttons412 on the PMSA 110. The media context assignments are stored at themedia delivery system 112 in the PMSA preset data 259 store.

FIG. 11 illustrates an example data structure 700 that may appear in adatabase of the media delivery system 112 such as the user accounts 240database within the media server application 212 or the PMSA preset data259 within the personal media streaming appliance server application 250as shown in FIG. 3. In this embodiment, the data in the media deliverysystem 112 may be represented with a plurality of tables whichidentifies a rational nature of the database according to the embodimentof the present disclosure. However, in alternative embodiments, the datastored in the media delivery system 112 may also be implemented usingother database models.

In the illustrated example, the data structure 700 includes a useraccount table 702, a media context table 704, and a media content itemtable 706. For each user account, the data structure 700 includes anorder data table 708, a device data table 710, a device setting table712, a preset table 714, a playback state table 716, and a taste profiletable 718.

The user account table 702 can be configured to include data usable toidentify users associated with user accounts of the media deliverysystem 112 (e.g., a media content provider or a media streamingservice). In some embodiments, the user account table 702 can be used tostore and identify the user accounts 240 as described with reference toFIG. 3. In some embodiments, the user account table 702 can referenceone or more other tables, and/or be referenced by one or more othertables. Some embodiments of the user account table 702 can contain afield for user account identifiers (IDs) 720, a field for useridentifiers (IDs) 722, a field for passwords 724, and a field forsubscription types 726.

The user account ID field identifies a plurality of user account IDs 720associated with the user accounts of the media delivery system 112.

The user ID field identifies user IDs 722 associated with the useraccounts.

The password field identifies passwords 724 associated with the useraccounts.

The subscription type field identifies subscription types 726 associatedwith the user accounts. Examples of the subscription types 726 include afree subscription and a fee-based subscription with a single tier orwith multiple tiers. Such a fee-based subscription can provide servicesthat the free subscription does not provide.

In other embodiments, the user account table 702 can contain additionalfields, such as biographical information (e.g., address, contactinformation, age, gender, birth date/year, family, relationships, work,education, etc.). It is noted that, where user data is used, it can behandled according to a defined privacy policy. User data can be handledin an anonymized matter.

Referring still to FIG. 11, each user account that can be identified inthe user account table 702 is associated with, and identifies, a set ofdata for providing various services from the media delivery system 112.In some embodiments, such a set of data includes an order data table708, device data table 710, a device setting table 712, a preset table714, a playback state table 716, and a taste profile table 718. In theillustrated example, the tables 708, 710, 712, 714, 716, and 718 areprimarily described to be associated with a single user account (e.g.,User Account ID: ABC). However, it is understood that, in otherembodiments, the tables 708, 710, 712, 714, 716, and 718 can bestructured to be associated with a plurality of user accounts

The order data table 708 identifies one or more orders associated with aparticular user account. (e.g., User Account ID: ABC in FIG. 9). Theorders are generally for PMSA devices. In some embodiments, the orderdata table 708 can be referenced by the user account table 702. Othertables can reference the order data table 708. The order data table 708can also reference one or more other tables. The order data table 708can contain a field for order identifiers (IDs) 730, a field for devicenames 732, and a field for order status 734. The order IDs 730 caninclude an order confirmation number or other unique identifiers. Thedevice names 732 correspond to devices involved in the order. The status734 indicates the latest event that has occurred in the orderfulfillment process. For example, the order status 734 can indicatewhether the device has been ordered, has shipped, or has been delivered.

The device data table 710 identifies one or more devices associated witha particular user account. In some embodiments, the device data table710 can be referenced by the user account table 702. Other tables canreference the device data table 710. The device data table 710 can alsoreference one or more other tables. The device data table 710 cancontain a field for device identifiers (IDs) 740, a field for devicenames 742, and a field for device status 744. The device ID fieldincludes one or more device IDs 740 of one or more media playbackdevices that are associated with the particular user account.

In some embodiments, a plurality of media playback devices, such as thePMSA 110, the computing device, and other computing devices, can berespectively used to access media content service from the mediadelivery system 112 which is associated with a single user account. Forexample, different media playback devices, such as the PMSA 110 and theuser computing device 102, can receive inputs of login information. Themedia content service associated with the user account can be providedto one or more of the media playback devices that have received logininformation associated with the same user account.

The device name field includes one or more device names 742 associatedwith the device IDs 740. The device status field identifies a devicestatus 744 for each of the media playback devices identified in thedevice data table 710. In some embodiments, the device status can beeither active or inactive. When the device status of a media playbackdevice is active, the media playback device is in operation andaccessible by the media delivery system 112 via the network 116. Whenthe device status of a media playback device is inactive, the mediaplayback device is not in operation and thus inaccessible by the mediadelivery system 112 via the network 116.

The device setting table 712 includes information about settings thatare configurable in one or more particular media playback devices. Insome embodiments, the device setting table 712 can be referenced by thedevice data table 710. Other tables can reference the device settingtable 712. The device setting table 712 can reference one or more othertables. In the illustrated example, the device setting table 712indicates that the media playback device identified by the device ID(“ABCsge”) has various settings, such as presets, playback settings,sound quality, notification, advertisement, and other user-configurablesettings.

The preset table 714 includes information about presets associated withone or more particular media playback devices. In some embodiments, thepreset table 714 can be referenced by the device setting table 712.Other tables can also reference the preset table 714. The preset table714 can reference one or more other tables. In the illustrated example,the preset table 714 contains information about the presets provided inthe media playback device identified by the device ID (“ABCsge”).

Some embodiments of the preset table 714 include a field for presetidentifiers (IDs) 750 and a field for media context identifiers (IDs)752. The preset ID field contains one or more preset identifiers (IDs)750 that identify presets provided in the particular media playbackdevice. The context ID field contains one or more media contextidentifiers 752 associated with the preset identifiers 750,respectively. The media context identifiers 752 are used to identifymedia contexts 238, as described herein. In some embodiments, a mediacontext identifier is configured as a Uniform Resource Identifier (URI).

In the illustrated examples of FIG. 6, the PMSA 110 includes the presetbuttons 412, and the preset buttons 412 can be identified by the presetidentifiers 750. As the preset identifiers 750 are associated with themedia context identifiers 752 that identify media contexts, the presetbuttons 412 in the PMSA 110 can be used to retrieve the media contextsidentified by the media context identifiers 752.

The playback state table 716 includes information about playback of oneor more media contexts 238. In some embodiments, where a plurality ofmedia playback devices may be used to play media content associated witha particular user account, only one of the plurality of media playbackdevices can be used to play the media content while the other mediaplayback devices may not be used to play the same media contentsimultaneously. In these embodiments, the playback state table 716 isconfigured to indicate playback information of the media content that isin common among the plurality of media playback devices associated withthe particular user account. In other embodiments, the playback statetable 716 is configured to indicate playback information for each of themedia playback devices associated with the particular user account,where the media playback devices may be used independently to play mediacontent in different manners.

In some embodiments, the playback state table 716 contains a currentcontext 760, a current media content item (i.e., a current track) 762, aplayback mode 764, a playback speed 766, and a next media content item(i.e., a next track) 768. In addition or alternatively, the playbackstate table 716 can contain other playback-related information. In someembodiments, the playback state table 716 can reference one or moreother tables, and/or be referenced by one or more other tables. Thecurrent context 760 indicates a media context 238 that is beingcurrently played in a media playback device. The current media contentitem 762 indicates a media content item that is being currently playedfrom the current context 760. The playback mode 764 indicates a playbackmode that is currently selected. Examples of the playback mode include anormal playback mode, a repeat playback mode, and a shuffle playbackmode. The playback speed 766 indicates a playback speed that iscurrently selected. Examples of the playback speed include a normalplayback speed, one or more faster playback speeds, and one or moreslower playback speeds. The next media content item 768 indicates amedia content item that is in queue and will be subsequently playedafter the current media content item 762.

Referring still to FIG. 11, the taste profile table 718 is configured toidentify a taste profile 242 (FIG. 3) associated with the particularuser account. In some embodiments, the taste profile table 718 can bereferenced by the user account table 702. Other tables can reference thetaste profile table 718. The taste profile table 718 can also referenceone or more other tables.

With reference still to FIG. 11, the media context table 704 isconfigured to identify one or more media contexts 238 as described withreference to FIG. 3. As illustrated, some embodiments of the mediacontext table 704 can respectively identify a media context 238 by amedia context identifier 752. The media context table 704 containsvarious pieces of information about a corresponding media context 238.Examples of such information include a media context title 780, a mediacontext type 782, a media context artist 784, a media context genre 786,and a list of media content items 788 associated with the media context238. Other information can also be included in the media context table704.

The media context title 780 indicates a title of the media context 238.The media context type 782 indicates a type of the media context 238,such as a playlist, an album, an artist, and a track. The media contextartist 784 indicates one or more artists associated with the mediacontext 238. The media context genre 786 indicates a genre associatedwith the media context 238. The list of media content items 788indicates one or more media content items (i.e., tracks) associated withthe media context 238. Each of the media content items can be identifiedby a track identifier 790. In some embodiments, one or more of the mediacontent items 234, as described with reference to FIG. 3, are identifiedby the list of media content items 788.

The media content item table 706 is configured to identify one or moremedia content items (i.e., tracks) 792 by the track identifiers 790. Insome embodiments, a track identifier is configured as a Uniform ResourceIdentifier (URI). In some embodiments, one or more of the media contentitems 792 are selected from the media content items 234 as describedwith reference to FIG. 3. The media content item table 706 can furtherinclude various attributes about the media content item 792, such as amedia content item title, artist identification (e.g., individual artistname or group name, or multiple artist names or group names), genre,era, and other attributes of the media content item.

FIG. 12 illustrates an example environment 800 in which a PMSA 110system is operated in a vehicle V to stream media content for playback.The vehicle V includes a dashboard 802 or a head unit 804. Theenvironment 800 includes one or more media playback devices configuredto play media content, such as a personal media streaming appliance(PMSA) system 110 and a vehicle media playback system 114. Theenvironment 800 further includes a data communication network 116.

In the example of FIG. 12, a user has received a new PMSA 110 and hasmounted the portable device inside of the vehicle V. In this example,the PMSA 110 is mounted to the head unit 804 of the vehicle V, but couldalso be mounted to the dashboard 802. In other embodiments, the PMSAsystem 110 can be configured to be built in a structure of the vehicleV.

The PMSA 110 is configured to receive media content personalized to theuser account as soon as the PMSA 110 is powered on. In some embodiments,input is received from actuation of a preset button 412 on the PMSA 110.Receiving input from a button triggers the PMSA 110 to retrieve mediacontent and/or setting information. This process is described furtherwith respect to FIG. 14.

The vehicle media playback system 114 operates to receive media contentfrom the PMSA system 110 and generates a media output 124 to play themedia content in the vehicle V. An example of the vehicle media playbacksystem 114 is illustrated and described in further detail herein, suchas with reference to FIG. 13.

FIG. 13 is a block diagram of an example embodiment of the vehicle mediaplayback system 114. In this example, the vehicle media playback system114 includes a vehicle head unit 804, an amplifier 806, and a speaker808.

The vehicle head unit 804 is configured to receive input and generatemedia content from various sources. In this example, the vehicle headunit 804 includes a receiver 810, a wireless communication device 812, awired input device 814, a processing device 816, a memory device 818, aninput assembly 820, a display device 822, and a stored media interfaceassembly 824.

The receiver 810 operates to receive media content signals from variousexternal sources. The received signals can then be used to generatemedia output by the vehicle media playback system 114. Some embodimentsof the receiver 810 include one or more tuners for receiving radiosignals such as FM or AM radio signals. Other embodiments of thereceiver 810 include a receiver for receiving satellite radio signalsand/or a receiver for receiving internet radio signals.

The wireless communication device 812 operates to communicate with otherdevices using wireless data signals. The wireless communication device812 can include one or more of a Bluetooth transceiver and a Wi-Fitransceiver. The wireless data signal may comprise a media contentsignal such as an audio or video signal. In some embodiments, thewireless communication device 812 is used to enable the vehicle mediaplayback system 114 to wirelessly communicate with the PMSA system 110and receive the media content signal 164 (FIG. 2) from the PMSA system110 via an in-vehicle wireless network.

The wired input device 814 provides an interface configured to receive acable for providing media content and/or commands. The wired inputdevice 814 includes an input connector 456 configured to receive a plugextending from a media playback device for transmitting a signal formedia content. In some embodiments, the wired input device 814 caninclude an auxiliary input jack (AUX) for receiving a plug from a mediaplayback device that transmits analog audio signals. The wired inputdevice 814 can also include different or multiple input jacks forreceiving plugs from media playback devices that transmit other types ofanalog or digital signals (e.g., USB, HDMI, Composite Video, YPbPr,DVI). In some embodiments, the wired input device 814 is also used toreceive instructions from other devices.

In some embodiments, the wired input device 814 provides the inputconnector 456 (e.g., an AUX port) for receiving a connector 452extending from the PMSA system 110, as illustrated in FIG. 6. The mediacontent signal 164 is then transmitted from the PMSA system 110 to thevehicle media playback system 114 via the cable 450, the connector 452,and the input connector 456.

The processing device 816 operates to control various devices,components, and elements of the vehicle media playback system 114. Theprocessing device 816 can be configured similar to the processing device148 (FIG. 2) and, therefore, the description of the processing device816 is omitted for brevity purposes.

In some embodiments, the processing device 816 operates to process themedia content signal 164 received from the PMSA system 110 and convertthe signal 164 to a format readable by the vehicle media playback system114 for playback.

The memory device 818 is configured to store data and instructions thatare usable to control various devices, components, and elements of thevehicle media playback system 114. The memory device 818 can beconfigured similar to the memory device 150 (FIG. 2) and, therefore, thedescription of the memory device 818 is omitted for brevity purposes.

The user input assembly 820 includes one or more input devices forreceiving user input from users for controlling the vehicle mediaplayback system 114. In some embodiments, the input assembly 820includes multiple knobs, buttons, and other types of input controls foradjusting volume, selecting sources and content, and adjusting variousoutput parameters. In some embodiments, the various input devices aredisposed on or near a front surface of the vehicle head unit 804. Thevarious input devices can also be disposed on the steering wheel of thevehicle or elsewhere. Additionally or alternatively, the input assembly820 can include one or more touch sensitive surfaces, which can beincorporated in the display device 822.

The display device 822 displays information. In some embodiments, thedisplay device 822 includes a liquid crystal display (LCD) panel fordisplaying textual information about content and/or settings of thevehicle media playback system 114. The display device 822 can alsoinclude other types of display panels such as a light emitting diode(LED) panel. In some embodiments, the display device 822 can alsodisplay image or video content.

The stored media interface assembly 824 reads media content stored on aphysical medium. In some embodiments, the stored media interfaceassembly 824 comprises one or more devices for reading media contentfrom a physical medium such as a compact disc or cassette tape.

The amplifier 806 operates to amplify a signal received from the vehiclehead unit 804 and transmits the amplified signal to the speaker 808. Inthis manner, the media output 124 can be played back at a greatervolume. The amplifier 806 may include a power source to power theamplification.

The speaker 808 operates to produce an audio output (e.g., the mediaoutput 124) based on an electronic signal. The speaker 808 can includeone or more vehicle embedded speakers 830 disposed at various locationswithin the vehicle V. In some embodiments, separate signals are receivedfor at least some of the speakers (e.g., to provide stereo or surroundsound).

In other embodiments, the speaker 808 can include one or more externalspeakers 832 which are arranged within the vehicle V. One or moreexternal speakers 832 can be connected to the vehicle head unit 804using a wired interface or a wireless interface. In some embodiments,the external speakers 832 can be connected to the vehicle head unit 804using Bluetooth. Other wireless protocols can be used to connect theexternal speakers 832 to the vehicle head unit 804. In otherembodiments, a wired connection (e.g., a cable) can be used to connectthe external speakers 832 to the vehicle head unit 804. Examples of thewired connection include an analog or digital audio cable connection anda universal serial bus (USB) cable connection. The external speaker 832can also include a mechanical apparatus for attachment to a structure ofthe vehicle.

FIG. 14 illustrates an example ecosystem 900 for the PMSA system 110 ofFIG. 1. In some embodiments, the ecosystem 900 is implemented at leastin part with the system 100 as illustrated and described in FIG. 1. Forexample, the ecosystem 900 includes the PMSA system 110, the mediadelivery system 112, and a user computing device 102. As describedherein, the PMSA system 110, the media delivery system 112, and the usercomputing device 102 can be in data communication via the network 116 asillustrated in FIG. 1.

In some embodiments, the ecosystem 900 is configured to providepersonalized media content to the PMSA 110 before first operation of thePMSA 110. At the time the PMSA 110 is ordered, the media delivery system112 assigns media contexts to each of a plurality of preset buttons 412,as discussed in FIG. 10. Updates can be made to the contexts selectedfor each preset button 412 based on one or both of new media consumptionthrough the user's media streaming account, and changes made to thesettings of the PMSA in response to inputs received from a usercomputing device 102. These updates can be made up until the moment thatthe PMSA 110 is first powered on.

The user computing device 102 includes the music playback application294 as described with reference to FIGS. 1 and 4. The music playbackapplication 294 includes a user interface operable to request mediacontent for playback on the user computing device 102. A media contentrequest 902 is communicated to the media delivery system 112. The mediaserver application 212 generates a media content stream 904 that iscommunicated back to the user computing device 102 for playback. Themedia content request 902 is analyzed and used to update the tasteprofile 242.

The music playback application 294 includes user settings 296 that canbe modified through the user interface 298. Inputs are received throughthe user interface 298 to modify user settings 296. The user settings296 can include settings for the PMSA 110. When a PMSA setting ismodified at the music playback application 294, a PMSA setting request906 is communicated to the media delivery system 112. The personal mediastreaming appliance configuration engine 258 receives the request andupdates the PMSA preset data 259 for the appliance associated with theuser account. Then personal media streaming appliance server application250 returns a PMSA setting confirmation 908 to the user computing device102.

Referring still to FIG. 14, the media delivery system 112 includes themedia server application 212 and the PMSA server application 250 (asdescribed also in FIG. 3). The PMSA server application 250 can includethe PMSA configuration engine 258 which includes an applianceprovisioning engine 126 and PMSA preset data 259.

In some embodiments, the PMSA configuration engine 258 operates toreceive the PMSA setting request 906 from the computing device 102 andupdate the PMSA preset data 259. The PMSA configuration engine 258continually updates the PMSA preset data 259 as each taste profile 242is updated. As media content is played on the user computing device 102,the media server application 212 updates the taste profile 242. Thepersonal media streaming appliance configuration engine 258 then updatesthe PMSA preset data 259. The PMSA preset data 259 includes assignmentsof media contexts to preset buttons 412. In embodiments where the PMSAhas been ordered for delivery, the PMSA preset data 259 is updated upuntil the point when the PMSA 110 is first powered on. The PMSA 110 isconfigured to receive the PMSA preset data 259 upon receiving a commandto power on.

The appliance provisioning engine 126 operates to ensure that the PMSA110 and its settings are linked to the correct user streaming account.The link provided by the appliance provisioning engine 126 is utilizedto determine which settings and media content are communicated to thePMSA 110 when it is first powered on.

Upon powering on the PMSA 110, some preset data, media content, and/orconfiguration information may be immediately communicated from the mediadelivery system 112 to the PMSA 110. In other embodiments, the mediadelivery system 112 stores all of the configuration data and mediacontent for the PMSA 110 in the cloud.

The preset-based media delivery engine 910 of the media delivery system112 operates to determine media content associated with one or more ofthe preset buttons 412 of the PMSA system 110. In some embodiments, thepreset-based media delivery engine 910 operates to receive a presetsignal 912 from the PMSA system 110 and determine which media contentcontext is associated with the corresponding preset signal 912 and useraccount. The preset signal 912 is further described in FIG. 15. In someembodiments, the preset signal 912 is generated at the PMSA system 110upon receiving an input of selecting a preset button 412. In theseembodiments, the selection (or activation) of the preset button 412 isregarded as a preset signal source. The preset signal 912 can includeinformation that identifies the preset button 512 selected at the PMSAsystem 110. The preset signal 912 is used by the preset-based mediadelivery engine 910 to identify media content associated with the presetbutton 412.

When the media delivery system 112 identifies the media content based onthe preset signal 912, the media delivery system 112 transmits a mediacontent stream 914 to the PMSA system 110 for playback.

FIG. 15 is a block diagram that illustrates an example of the presetsignal 912 of FIG. 14. In some embodiments, the preset signal 912includes user account ID 930, device ID 932, and preset button ID 934.

The user account information 930 includes information that identifiesuser accounts that are associated with PMSA systems 110. In someembodiments, the user account information 930 includes user accountidentifiers for identifying the user accounts that match the respectivePMSA systems 110. A user account identifier can be a string of numbersand/or letters that identify a user account. An example of the useraccount information 930 is illustrated and described in more detail withreference to FIG. 11.

In some embodiments, when the media delivery system 112 receives thepreset signal 912, the media delivery system 112 can retrieve the useraccount information 930 and determine a user account that matches thepreset signal 912. For example, the PMSA setting request 606 can includea user account identifier that identifies a user account associated withthe PMSA system 110, and the media delivery system 112 can process thepreset signal 912 and look up the user account information 930 todetermine which user account in the user account information 930 isassociated with the PMSA system 110.

In other embodiments, the preset signal 912 does not include useraccount ID 930. The media delivery system 112 can rely on the device ID932 to look up the account with which the PMSA system 110 is associated.

The device ID 932 includes information that identifies one or more PMSAsystems 110. In some embodiments, the device ID 932 includes deviceidentifiers for identifying PMSA systems 110. A device identifier can bea string of numbers and/or letters that identify a PMSA system. Anexample of the device ID 932 is illustrated and described in more detailwith reference to FIG. 11.

The preset button ID 934 includes information about the preset buttons412 of the PMSA systems 110, such as preset identifiers that identifythe preset buttons 412. A preset identifier can be a string of numbersand/or letters that identify a preset button. In some embodiments, thepreset button ID 934 further includes media content that is associatedwith the preset buttons 412. An example of the preset button ID 934 isillustrated and described in more detail with reference to FIG. 11.

FIG. 16 is a block diagram that illustrates an example of the PMSApreset data 259 of FIG. 14. In some embodiments, the PMSA preset data259 include user account information 1002, device information 1004,preset information 1006, device status information 1008, and mediaplayback state information 1010.

The PMSA preset data 259 include information associated with the presetbuttons 412 of the PMSA system 110. In some embodiments, the PMSA presetdata 259 includes information for a plurality of PMSA systems 110 andcan be used by the media delivery system 112 to control the plurality ofPMSA systems 110. In other embodiments, the PMSA preset data 259 can bededicated to a single PMSA system 110 or a limited group of PMSAsystems.

The user account information 1002 includes information that identifiesuser accounts that are associated with PMSA systems 110, respectively.In some embodiments, the user account information 1002 includes useraccount identifiers for identifying the user accounts that match therespective PMSA systems 110. A user account identifier can be a stringof numbers and/or letters that identify a user account. An example ofthe user account information 1002 is illustrated and described in moredetail with reference to FIG. 11.

In some embodiments, when the media delivery system 112 receives thepreset signal 912, the media delivery system 112 can retrieve the useraccount information 1002 and determine a user account that matches thepreset signal 912. For example, the preset signal 912 can include a useraccount identifier that identifies a user account associated with thePMSA system 110, and the media delivery system 112 can process thepreset signal 912 and look up the user account information 1002 todetermine which user account in the user account information 1002 isassociated with the PMSA system 110.

The device information 704 includes information that identifies one ormore PMSA systems 110. In some embodiments, the device information 704includes device identifiers for identifying PMSA systems 110. A deviceidentifier can be a string of numbers and/or letters that identify aPMSA system. An example of the device information 704 is illustrated anddescribed in more detail with reference to FIG. 11.

In some embodiments, when the media delivery system 112 receives thepreset signal 912, the media delivery system 112 can retrieve the deviceinformation 1004 and determine a device identifier that matches thepreset signal 912. For example, the preset signal 912 can include adevice identifier that identifies the PMSA system 110, and the mediadelivery system 112 can process the preset signal 912 and look up thedevice information 1004 to determine which PMSA system matches thedevice identifier included in the preset signal 912.

The preset information 1006 includes information that identifies one ormore preset buttons 412 of PMSA systems 110. In some embodiments, thepreset information 1006 includes preset identifiers for identifyingpreset buttons of PMSA systems 110. A preset identifier can be a stringof numbers and/or letters that identify a preset button of a PMSAsystem. An example of the preset information 1006 is illustrated anddescribed in more detail with reference to FIG. 11.

In some embodiments, when the media delivery system 112 receives thepreset signal 912, the media delivery system 112 can retrieve the presetinformation 1006 and determine a preset button identifier that matchesthe preset signal 912. For example, the preset signal 912 can include apreset button identifier that identifies a preset button of a PMSAsystem 110. The media delivery system 112 can process the preset signal912 to look up the preset information 1006. The preset information 1006is used to determine which preset button matches the preset buttonidentifier included in the preset signal 912.

The device status information 1008 includes information about statusesof PMSA systems 110. Each of the PMSA systems 110 can be in either anactive state or an inactive state. In some embodiments, when a PMSAsystem 110 is in an active state, the PMSA system 110 is in operationand accessible by the media delivery system 112 via the network 116.When a PMSA system 110 is in an inactive state, the PMSA system 110 isnot in operation and inaccessible by the media delivery system 112 viathe network 116.

The media playback state information 1010 includes information aboutmedia content playback via PMSA systems 110. In some embodiments, themedia playback state information 1010 is provided for each user account.In other embodiments, the media playback state information 1010 isprovided for each media playback device. In yet other embodiments, themedia playback state information 1010 is provided for each mediacontext. In still other embodiments, the media playback stateinformation 1010 is provided for each media content item.

In some embodiments, the media playback state information 1010 includescurrent context information 1030, current track information 1032,current position-in-track information 1034, playback control statusinformation 1036, playback settings information 1038, subsequent trackinformation 1040, and playback history information 1042.

The current context information 1030 includes information about a mediacontext that is being currently played.

The current track information 1032 includes information about a mediacontent item (e.g., track) that is currently being played. Thecurrently-playing media content item can be one of the media contentitems included in the currently-playing media context.

The current position-in-track information 1034 includes informationabout a current playback position of the media context. For example, thecurrent position-in-track information 1034 includes a time (e.g., anelapsed time or progress time) that has elapsed since the beginning ofplayback of the media context. In other embodiments, the currentposition-in-track information 1034 includes a remaining time until themedia context is complete to play. In other embodiments, the currentposition-in-track information 1034 can be configured for a particularmedia content item.

The playback control status information 1036 includes information thatindicates whether the current media content item is currently beingplayed or stopped (including paused).

The playback settings information 1038 include information about one ormore settings of PMSA systems 110. Examples of the settings of PMSAsystems 110 include preset information, playback settings, sound qualitysettings, notification settings, advertisement settings, and othersettings for controlling operation of the PMSA systems 110 or mediacontent playback via the PMSA systems 110.

The subsequent track information 1040 includes information about a mediacontent item (e.g., track) that is to be played after the current mediacontent item. In some embodiments, the subsequent track information 1040identifies a single media content item. In other embodiments, thesubsequent track information 1040 identifies a plurality of mediacontent items in order.

The playback history information 1042 includes information about themedia content items that have been played. In some embodiments, theplayback history information 1042 can be provided as the playbackhistory by each user account. In other embodiments, the playback historyinformation 1042 can be provided as the playback history by each mediaplayback device.

The various examples and teachings described above are provided by wayof illustration only and should not be construed to limit the scope ofthe present disclosure. Those skilled in the art will readily recognizevarious modifications and changes that may be made without following theexamples and applications illustrated and described herein, and withoutdeparting from the true spirit and scope of the present disclosure.

The invention claimed is:
 1. A system for providing personalized mediacontent to a personal media streaming appliance (PMSA), the systemcomprising: a media delivery system comprising: a media content servercomprising: a processing device, a memory device, and a media serverapplication configured to provide a media streaming service; and apersonal media streaming appliance server comprising: a processingdevice, a memory device, and a personal media streaming applianceconfiguration engine configured to: store an identifier associated witha user media streaming account of a user and an identifier associatedwith a personal media streaming appliance in a table to link the usermedia streaming account to the personal media streaming appliancewithout user input that is received upon or after the PMSA's first useby the user; automatically determine personalized content to provide tothe personal media streaming appliance upon first use by the user;automatically select one or more media contexts, wherein thepersonalized content matches the one or more media contexts; and assignthe one or more media contexts to a plurality of preset settings of thepersonal media streaming appliance before the PMSA's first use by theuser.
 2. The system of claim 1, wherein the media server applicationcomprises user accounts data and taste profiles data for each of aplurality of users and the personal media streaming applianceconfiguration engine utilizes the taste profiles data for determiningpersonalized content.
 3. The system of claim 1, wherein the personalmedia streaming appliance configuration engine comprises an applianceprovisioning engine configured to automatically assign media contexts toeach of a plurality of preset buttons of the personal media streamingappliance, and a PMSA preset data store configured to store informationregarding the assigned media contexts for each preset setting of thepersonal media streaming appliance.
 4. The system of claim 3, whereinthe personal media streaming appliance configuration engine receives anappliance identifier from a user computing device.
 5. The system ofclaim 1, further comprising: a personal media streaming appliance systemcomprising: a user input device; a media content output device; and amemory device comprising an appliance setting configuration engineconfigured to receive personalized settings for outputting media contentfrom the media delivery system.
 6. The system of claim 5, wherein thepersonal media streaming appliance system comprises at least 3 presetbuttons and the appliance provisioning engine assigns a unique contextto each of the preset buttons, wherein each unique context is one of analbum, an artist, a genre, a podcast, a radio station, an audiobook, anda playlist.
 7. The system of claim 5, wherein the personal mediastreaming appliance system is configured to output media contentpersonalized for the user account of the user upon first use by the userwithout receiving input from physical controls.
 8. The system of claim1, wherein: the storing the identifier associated with the user mediastreaming account of the user and the identifier associated with thepersonal media streaming appliance comprises storing the identifierassociated with the user media streaming account of the user and theidentifier associated with the personal media streaming appliance beforethe user receives the PMSA from a vendor; and the assigning the one ormore media contexts to the plurality of preset settings of the PMSAcomprises assigning the one or more media contexts to the plurality ofpreset settings of the PMSA before the user receives the PMSA from thevendor.
 9. A method for providing personalized media content to apersonal media streaming appliance, the method comprising the steps of:providing, by a media content server executing a media serverapplication, a media streaming service; linking, by a personal mediastreaming appliance configuration engine, a user media streaming accountof a user to a personal media streaming appliance without user inputthat is received upon or after the PMSA's first use by the user bystoring an identifier associated with the user media streaming accountand an identifier associated with the personal media streaming appliancein a table; automatically determining personalized content to provide toa personal media streaming appliance upon first use by the user;automatically selecting one or more media contexts, wherein thepersonalized content matches one or more media contexts; and assigningthe one or more media contexts to a plurality of preset settings of thepersonal media streaming appliance before the PMSA's first use by theuser.
 10. The method of claim 9, further comprising the steps of:storing, by the media server application, user accounts data and tasteprofiles data for each of a plurality of users; and determining, by thepersonal media streaming appliance configuration engine, personalizedcontent based on the taste profiles data.
 11. The method of claim 9,further comprising the steps of: assigning, by an appliance provisioningengine, media contexts to each of the plurality of preset buttons of thepersonal media streaming appliance; and storing, by a PMSA preset datastore, information regarding the assigned media contexts for each presetsetting of the personal media streaming appliance.
 12. The method ofclaim 11, further comprising: receiving, by the personal media streamingappliance configuration engine, an appliance identifier from a usercomputing device.
 13. The method of claim 9, further comprising the stepof: receiving, by an appliance setting configuration engine,personalized settings for outputting media content from a media deliverysystem.
 14. The method of claim 13, further comprising the step of:assigning a unique context to each of at least 3 preset buttons of thepersonal media streaming appliance, wherein each unique context is oneof an album, an artist, a genre, a podcast, a radio station, anaudiobook, and a playlist.
 15. The method of claim 13, furthercomprising the step of: outputting media content personalized for theuser account of the user upon first use without receiving input fromphysical controls.
 16. The system of claim 9, wherein: the storing theidentifier associated with the user media streaming account of the userand the identifier associated with the personal media streamingappliance comprises storing the identifier associated with the usermedia streaming account of the user and the identifier associated withthe personal media streaming appliance before the user receives the PMSAfrom a vendor; and the assigning the one or more media contexts to theplurality of preset settings of the PMSA comprises assigning the one ormore media contexts to the plurality of preset settings of the PMSAbefore the user receives the PMSA from the vendor.
 17. A non-transitorycomputer-readable medium having stored thereon one or more sequences ofinstructions for causing one or more processors to perform: providing,by a media content server executing a media server application, a mediastreaming service; linking, by a personal media streaming applianceconfiguration engine, a user media streaming account of a user to apersonal media streaming appliance without user input that is receivedupon or after the PMSA's first use by the user by storing an identifierassociated with the user media streaming account of the user and anidentifier associated with the personal media streaming appliance in atable; automatically determining, without user input, personalizedcontent to provide to the personal media streaming appliance upon firstuse; automatically selecting one or more media contexts, wherein thepersonalized content matches one or more media contexts; and assigningthe one or more media contexts to a plurality of preset settings of thepersonal media streaming appliance before the PMSA's first use by theuser.
 18. The computer-readable medium of claim 17, further havingstored thereon a sequence of instructions for causing the one or moreprocessors to perform: storing, by the media server application, useraccounts data and taste profiles data for each of a plurality of users;and determining, by the personal media streaming appliance configurationengine, personalized content based on the taste profiles data.
 19. Thecomputer-readable medium of claim 17, further having stored thereon asequence of instructions for causing the one or more processors toperform: assigning, by an appliance provisioning engine, media contextsto each of the plurality of preset buttons of the personal mediastreaming appliance; and storing, by a PMSA preset data store,information regarding the assigned media contexts for each presetsetting of the personal media streaming appliance.
 20. Thecomputer-readable medium of claim 19, further having stored thereon asequence of instructions for causing the one or more processors toperform: receiving, the personal media streaming appliance configurationengine, an appliance identifier from a user computing device.
 21. Thecomputer-readable medium of claim 17, further having stored thereon asequence of instructions for causing the one or more processors toperform: receiving, by an appliance setting configuration engine,personalized settings for outputting media content from a media deliverysystem.
 22. The computer-readable medium of claim 21, further havingstored thereon a sequence of instructions for causing the one or moreprocessors to perform: assigning a unique context to each of at least 3preset buttons of the personal media streaming appliance, wherein eachunique context is one of an album, an artist, a genre, a podcast, aradio station, an audiobook, and a playlist.
 23. The computer-readablemedium of claim 21, further having stored thereon a sequence ofinstructions for causing the one or more processors to perform:outputting media content personalized for the user account of the userupon first use by the user without receiving input from physicalcontrols.
 24. The system of claim 17, wherein: the storing theidentifier associated with the user media streaming account of the userand the identifier associated with the personal media streamingappliance comprises storing the identifier associated with the usermedia streaming account of the user and the identifier associated withthe personal media streaming appliance before the user receives the PMSAfrom a vendor; and the assigning the one or more media contexts to theplurality of preset settings of the PMSA comprises assigning the one ormore media contexts to the plurality of preset settings of the PMSAbefore the user receives the PMSA from the vendor.